diff options
author | Gar <gar+gh@danger.computer> | 2022-07-13 16:32:38 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-07-13 16:32:38 +0300 |
commit | 2dfa8a483629bdd667071b7ac4b5a037612e7f62 (patch) | |
tree | 98ee0660a250dcc63138216b36f054891c13782b | |
parent | 45a9bdee604073a3c5b4d3c6d90e22bf6672d6bf (diff) |
chore: suggest dogfooding npm when developing it (#5159)
Some folks may be running older versions of npm globally, or maybe even
have aliased another package manager to `npm`. This will ensure the
latest npm source is running when developing the cli itself.
-rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 33dff2e8e..b32e47ce2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,7 +19,7 @@ $ git clone git@github.com:npm/cli.git npm **2. Navigate into project & install development-specific dependencies...** ```bash -$ cd ./npm && npm install +$ cd ./npm && node . install ``` **3. Write some code &/or add some tests...** @@ -30,7 +30,7 @@ $ cd ./npm && npm install **4. Run tests & ensure they pass...** ``` -$ npm run test +$ node . run test ``` **5. Open a [Pull Request](https://github.com/npm/cli/pulls) for your work & become the newest contributor to `npm`! 🎉** @@ -42,7 +42,7 @@ We use [`tap`](https://node-tap.org/) for testing & expect that every new featur **You can find out what the current test coverage percentage is by running...** ```bash -$ npm run check-coverage +$ node . run check-coverage ``` ## Performance & Benchmarks |