npm-pkg-gen
commitlint
npm-pkg-gen | commitlint | |
---|---|---|
1 | 28 | |
0 | 16,022 | |
- | 1.0% | |
0.0 | 9.6 | |
almost 2 years ago | 3 days ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
npm-pkg-gen
-
How to make an npm package with an automated workflow
Voila! We're done. Hopefully, you found this post useful. Do checkout the npm-pkg-gen package if you want to get going fast, and star it on Github if you like it!
commitlint
-
Streamline Your Workflow: A Guide to Normalising Git Commit and Push Processes
commitlint is the most important tool we need for this step.
-
How to use Lefthooks in your node project?
Apart from these we also need to enforce standards for all our commit messages(commit-lint).
-
Better Git Commits with `@commitlint`
There are many features of commitlint that I can't mention one by one, as well as installation guide. To know the detail you can directly access https://github.com/conventional-changelog/commitlint.
-
Conventional Commit Message and Linting
These commit message prefixes can help to provide context and organization in a project's version control history, making it easier to understand and track changes over time. Note: if you want to force these rules on commit messages, here is a commit linting lib for you. Commitlint
-
Nodejs Boilerplate with Typescript and Express
Commit Lint
-
Setting Up a Modern Preact Application With Typescript, Vite and Vitest
I personally find it quite useful to enforce a uniform commit style. commitlint pairs well with husky.
-
How to enforce Conventional Commit messages using Git hooks with husky & commitlint
β§ input: Set up Conventional Commits using Husky and commitlint β subject may not be empty [subject-empty] β type may not be empty [type-empty] β found 2 problems, 0 warnings β Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint husky - commit-msg hook exited with code 1 (error)
-
Commit message linting within Magit?
Can setup tools like Commitlint to add hooks that will reject a commit message if it is invalid, but if you format a commit message incorrectly it simply closes the commit buffer and returns to git status, meaning you have to retype out your commit message, which is obviously less than ideal.
-
π Angular 14 + ESLint, Material + Transloco + Jest, TestCafe + Docker + Prettier π
β Angular 14 β Angular Material β Unit Testing with Jest β End-to-End Testing with TestCafΓ© β Internationalization with Transloco β Auto documentation with Compodoc β Analyse your project with source-map-explorer β Docker β ESLint β Prettier β Commit Linting
- Require commit-msg hook for all users...
What are some alternatives?
actions-workflow-samples - Help developers to easily get started with GitHub Action workflows to deploy to Azure
lint-staged - π«π© β Run linters on git staged files
semantic-release - :package::rocket: Fully automated version management and package publishing
husky - Git hooks made easy πΆ woof!
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
emoji-commit-messages - π΅ A fun paradigm to encourage cleaner commits.
create-nuxt-app - Create Nuxt.js App in seconds.
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
tslint - :vertical_traffic_light: An extensible linter for the TypeScript language
pretty-quick - β‘ Get Pretty Quick
vscode-commit-prompt - β Commit faster and cleaner with keybound formatted commit prompt for VS Code