Search Results for "npm"

...Ensures the working directory is clean and that there are no unpulled changes. Reinstalls dependencies to ensure your project works with the latest dependency tree. Ensures your Node.js and npm versions are supported by the project and its dependencies. Bumps the version in package.json and npm-shrinkwrap.json (if present) and creates a git tag. Prevents accidental publishing of pre-release versions under the latest dist-tag. Publishes the new version to npm, optionally under a dist-tag. Rolls back the project to its previous state in case publishing fails. ...

commitlint checks if your commit messages meet the conventional commit format. commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. ...

.../usr/local/bin). The downloads are kept in a cache folder to be used for reinstalls. The downloads are also available for limited use using n which and n run and n exec. The global npm packages are not changed by the install, with the exception of npm itself which is part of the Node.js install.

The conventional-changelog repo is managed as a monorepo; it's composed of many npm packages. It's recommended you use the high-level standard-version library, which is a drop-in replacement for npm's version command, handling automated version bumping, tagging, and CHANGELOG generation. Alternatively, if you'd like to move towards completely automating your release process as an output from CI/CD, consider using semantic-release.

...Get instant feedback on your commit message formatting and be prompted for required fields. Commitizen is currently tested against Node.js 12, 14, & 16, although it may work in older versions of Node.js. You should also have npm 6 or greater. When you're working in a Commitizen-friendly repository, you'll be prompted to fill in any required fields, and your commit messages will be formatted according to the standards defined by project maintainers. Installing and running Commitizen locally allows you to make sure that developers are running the exact same version of Commitizen on every machine.

Run linters against staged git files and don't let anything slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary shell tasks with a list of staged files as an...

Communicate important updates to your team via git commit messages. Sometimes you need to communicate changes to other developers on your project. In a small team, a Slack message works okay, but in larger teams and distributed organizations (such as open-source projects), reaching everyone can be a pain. git-notify allows you to embed announcements into your git commit messages. And display them to another developer on a machine, far far away. Just add "git-notify:" to your git commit...

Type git open to open the repo website (GitHub, GitLab, Bitbucket) in your browser. git open works with these hosted repo providers, git open --issue currently only works with GitHub, Visual Studio Team Services and Team Foundation Server. The preferred way of installation is to simply add the git-open script somewhere into your path (e.g. add the directory to your PATH environment or copy git-open into an existing included path like /usr/local/bin). Antigen will handle cloning the plugin...

...The hooks' working directory is relative to the git root (where you have your .git directory). This means that if your package.json is in a subdirectory of your git repository, you'll need to cd into the directory before running any npm scripts.