All interactions in the npm organization on GitHub are considered to be covered by our standard Code of Conduct.
1. Clone this repository...
$ git clone git@github.com:npm/cli.git2. Navigate into project & install development-specific dependencies...
$ cd ./npm && npm install3. Write some code &/or add some tests...
...4. Run tests & ensure they pass...
$ npm run test
5. Open a Pull Request for your work & become the newest contributor to npm! 馃帀
We expect that every new feature or bug fix comes with corresponding tests that validate the solutions. We strive to have as close to, if not exactly, 100% code coverage.
You can find out what the current test coverage percentage is by running...
$ npm run test-coverageWe've set up an automated benchmark integration that will run against all Pull Requests; Posting back a comment with the results of the run.
Example:
You can learn more about this tool, including how to run & configure it manually, here
When submitting a new bug report, please first search for an existing or similar report & then use one of our existing issue templates if you believe you've come across a unique problem. Duplicate issues, or issues that don't use one of our templates may get closed without a response.