Age | Commit message (Collapse) | Author |
|
|
|
|
|
In this node version, fall back to `util.promisify` of the callback version.
Maybe fixes https://github.com/npm/cli/issues/2623. Maybe fixes https://github.com/npm/cli/issues/2652. Maybe fixes https://github.com/npm/cli/issues/2625.
PR-URL: https://github.com/npm/cli/pull/2654
Credit: @ljharb
Close: #2654
Reviewed-by: @wraithgar, @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/2682
Credit: @ljharb
Close: #2682
Reviewed-by: @wraithgar
|
|
|
|
|
|
- fix prune target
- fix ci build
- run rebuild after install
PR-URL: https://github.com/npm/cli/pull/2068
Credit: @nlf
Close: #2068
Reviewed-by: @ruyadorno
|
|
|
|
We are targetting 100% test coverage for npm v7 GA. Using a
coverage-map, we require that any of the newly created tests fully cover
the module that they are testing. However, this has the side effect of
_always_ hitting 100% coverage when running 'npm test', even though not
all modules are being tested.
This adds a new 'load-all' test which, in 'check-coverage' mode, tells
nyc to include every file in the project.
This also removes the double-run of our tests in CI, where we run once
and then immediately run the same exact thing again for Coveralls, and
sends the 'check-coverage' output to Coveralls instead.
PR-URL: https://github.com/npm/cli/pull/1820
Credit: @isaacs
Close: #1820
Reviewed-by: @ruyadorno
|
|
Accidentally landed this in the v7 branch, didn't realize it was based on v6.
|
|
Update the matrix to have two Windows workflows: one running PowerShell
and one running bash.
|
|
|
|
|
|
|
|
|
|
|
|
trigger benchmark suite
|
|
|
|
This should be more consistent since it should use the specified standard version and not the latest one.
PR-URL: https://github.com/npm/cli/pull/604
Credit: @XhmikosR
Close: #604
Reviewed-by: @mikemimik
|
|
- Moved windows builds to travis-only since they're currently failing
on GHA and it's not code-related
- Added setup on GHA config to only run coverage once in ubuntu target
|
|
PR-URL: https://github.com/npm/cli/pull/600
Credit: @XhmikosR
Close: #600
Reviewed-by: @ruyadorno
|
|
This will allow all builds to run even if one fails
PR-URL: https://github.com/npm/cli/pull/601
Credit: @XhmikosR
Close: #601
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/278
Credit: @mikemimik
Close: #278
Reviewed-by: @claudiahdz
|
|
- This will ensure we inherit our standard labels from the `open-source-project-boilerplate`
PR-URL: https://github.com/npm/cli/pull/282
Credit: @darcyclarke
Close: #282
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/272
Credit: @JasonEtco
Close: #272
Reviewed-by: @ruyadorno
|
|
Refs: https://github.com/npm/cli/pull/5
PR-URL: https://github.com/npm/cli/pull/17/
Credit: @watilde
Reviewed-By: @zkat
|
|
`npm is doing something I don't understand.` is often inappropriately used when the author means `npm is producing incorrect or undesirable behavior.`. I only had to look thru the first page of open issues to find 5 examples of this.
PR-URL: https://github.com/npm/npm/pull/19893
Credit: @MrStonedOne
Reviewed-By: @zkat
|
|
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/15960
Credit: @watilde
Reviewed-By: @zkat
|
|
Credit: @AlexChesters
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/14010
|
|
- move important bits to top
- condense supporting info down to a smaller section
- more structured request for proxy & network info
|
|
|
|
- moved to .github to keep top-level directory clean
- expanded feature request section
- tweaked formatting
|