tiny-conventional-commits-parser is a JavaScript/TypeScript library specifically designed for lightweight and basic parsing of conventional commit messages. As of its current stable version, `0.1.0`, it provides essential functionalities for extracting structured information such as commit type, scope, description, and indicators for breaking changes from raw commit data or recent Git history. The package is in early but active development, evidenced by the recent `v0.1.0` feature release. A key differentiator and intentional design choice is its explicit aim *not* to provide feature or API compatibility with the more extensive `conventional-commits-parser` from the `conventional-changelog` monorepo. This makes it particularly suitable for environments or tools requiring minimal overhead and a focused approach to conventional commit parsing, without the broader feature set or potentially larger dependency footprint of alternative solutions. It ships with comprehensive TypeScript type definitions, enhancing developer experience and type safety.
npm install tiny-conventional-commits-parserVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to fetch recent commits from Git history between specified references and parse a raw commit object for its conventional commit structure, including breaking changes.
Review the specific API documentation for `tiny-conventional-commits-parser` and adapt code rather than assuming compatibility with other parsers.
Pin to exact versions in production environments and thoroughly test updates. Monitor the GitHub repository for release notes.
Verify that the library's capabilities meet your specific parsing requirements, especially for complex commit message structures or non-standard conventions. Consider contributing or requesting features if needed.
Consult the latest documentation or source code for `getRecentCommits` and its path filtering options. Experiment with different path inputs in a controlled environment to confirm expected behavior.
Ensure your project is configured for ESM and use `import { parseCommit } from 'tiny-conventional-commits-parser'`.Verify that the provided Git references (e.e.g. 'v0.0.1', 'HEAD', 'main') are valid and accessible within the current Git repository context where the command is executed.
Ensure commit messages adhere strictly to the Conventional Commits specification. The parser is designed for these formats, and non-compliant messages will result in less structured output or flags like `isConventional: false`.
No dependency data recorded yet.