Age | Commit message (Collapse) | Author |
|
Instead of files randomly requiring the npm singleton,
we pass it where it needs to go so that tests don't need
to do so much require mocking everywhere
PR-URL: https://github.com/npm/cli/pull/2772
Credit: @wraithgar
Close: #2772
Reviewed-by: @ruyadorno
|
|
Fix: https://github.com/npm/arborist/issues/207
PR-URL: https://github.com/npm/cli/pull/2573
Credit: @isaacs
Close: #2573
Reviewed-by: @nlf
|
|
|
|
Added a test for install too for this specific condition
PR-URL: https://github.com/npm/cli/pull/2455
Credit: @wraithgar
Close: #2455
Reviewed-by: @isaacs
|
|
`npm ci` should run all the same preinstall/install/postinstall/prepare
scripts for the root project just like `npm install`.
Fixes: #1905
PR-URL: https://github.com/npm/cli/pull/2316
Credit: @isaacs
Close: #2316
Reviewed-by: @ruyadorno
|
|
We have a lot of tests that were not handling errors in callbacks, not
defining variables, defining variables that weren't used, and just
generally not formatted like the rest of npm.
Hazard of moving fast. Thankfully, machines can help.
|
|
|
|
Fixes: #2017
Credit: @darcyclarke
Close: #2159
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/2083
Credit: @nlf
Close: #2083
Reviewed-by: @darcyclarke
|
|
Via: https://github.com/targos/npm7-cra#issue-1-npm-ci-changes-packagejson
|
|
PR-URL: https://github.com/npm/cli/pull/1523
Credit: @claudiahdz
Close: #1523
Reviewed-by: @ruyadorno
|