| Age | Commit message (Collapse) | Author |
|---|
|
PR-URL: https://github.com/npm/cli/pull/656
Credit: @isaacs
Close: #656
Reviewed-by: @mikemimik
|
|
PR-URL: https://github.com/npm/cli/pull/655
Credit: @isaacs
Close: #655
Reviewed-by: @mikemimik
|
|
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
|
|
PR-URL: https://github.com/npm/cli/pull/705
Credit: @clabe45
Close: #705
Reviewed-by: @mikemimik
|
|
- Fixes ability to run tests using an arbitrary node bin
- Fixes `make test-npm` in nodejs repo
- Added `tap-snapshots` folder
- Added required `.npmrc` root file
Fixes npm/statusboard#45
PR-URL: https://github.com/npm/cli/pull/696
Credit: @ruyadorno
Close: #696
Reviewed-by: @mikemimik
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In wondered why npm link doesn't "install to" `npm prefix`.
I looked up the documentation for `npm prefix` and found
the important distinction between the local prefix, and the
global prefix.
This attempts to clarity that `npm link` always uses specifically
the global prefix.
PR-URL: https://github.com/npm/cli/pull/532
Credit: @jgehrcke
Close: #532
Reviewed-by: @ruyadorno
|
|
tag -f
PR-URL: https://github.com/npm/cli/pull/648
Credit: @rhengles
Close: #648
Reviewed-by: @ruyadorno
|
|
- 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
|
|
Paired with @ruyadorno
PR-URL: https://github.com/npm/cli/pull/659
Credit: @isaacs
Close: #659
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/600
Credit: @XhmikosR
Close: #600
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/603
Credit: @XhmikosR
Close: #603
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
|
|
When you set `<cache>` directory in npm config, `npm ci` has been using `<cache>` for storing the cache instead of `<cache>/_cacache`
PR-URL: https://github.com/npm/cli/pull/550
Credit: @zhenyavinogradov
Close: #550
Reviewed-by: @ruyadorno
|
|
|
|
PR-URL: https://github.com/npm/cli/pull/569
Credit: @claudiahdz
Close: #569
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/627
Credit: @felixonmars
Close: #627
Reviewed-by: @ruyadorno
|
|
Not sure why this wasn't raised when I was running the release,
the tests definitely passed. Fixed now, at any rate.
|
|
|
|
|
|
Prevent a global install from overwriting bins and manpages if they are
not links/shims that npm controls, or if then are links/shims to
packages other than the one being installed.
Changes error message output on EEXIST errors to be more helpful.
Related:
- https://github.com/npm/bin-links/pull/12
- https://github.com/npm/gentle-fs/pull/7
Note: this does NOT prevent packages from overwriting one another's bins
in non-global package installs, because doing so would introduce a
[dependency hell](https://en.wikipedia.org/wiki/Dependency_hell) that
npm 6 is not capable of avoiding without significant refactoring. The
collision detection in npm v7's tree building will enable us to explore
such an option, by never placing dependencies in the same place if they
would write the same bin script. (It's fundamentally similar to
peerDependency resolution, but much simpler.)
Since users have not complained about this potential foot-gun in the
last 5 years, its unlikely that it is a significant issue, and
introducing additional dependency nesting (or worse, failing installs
for unresolveable trees) is likely an even worse hazard. If we do
prevent non-global-top installs from overwriting one another's bins, it
ought to be done only as best-effort (ie, allow the collision if both
deps need to be placed in the same node_modules folder) and perhaps
opt-in with a config flag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A few references to the `doc` target were not updated to `docs` in
https://github.com/npm/cli/pull/274 and resulted in `make release`
not building the docs.
PR-URL: https://github.com/npm/cli/pull/546
Credit: @richardlau
Close: #546
Reviewed-by: @mikemimik
|
|
PR-URL: https://github.com/npm/cli/pull/182
Credit: @Hoidberg
Close: #182
Reviewed-by: @mikemimik
|
|
PR-URL: https://github.com/npm/cli/pull/263
Credit: @woppa684
Close: #263
Reviewed-by: @mikemimik
|
|
Trying to open url for a package that is using the string shorthand is
currently broken using: `npm fund <pkg>`
This commit fixes the issue and adds the missing unit and integration
tests covering that usecase.
Fixes #498
PR-URL: https://github.com/npm/cli/pull/501
Credit: @ruyadorno
Close: #501
Reviewed-by: @mikemimik
|
|
PR-URL: https://github.com/npm/cli/pull/504
Credit: @Lighting-Jack
Close: #504
Reviewed-by: @mikemimik
|
|
Fix 'where' for file deps. It makes more sense for the 'where' to be the
directory the file is in (and was possibly built in) than it being the
file itself, having no use whatsoever.
See https://npm.community/t/3364
PR-URL: https://github.com/npm/cli/pull/142
Credit: @larsgw
Close: #142
Reviewed-by: @mikemimik
|
|
This reverts commit 3471d5200217bfa612b1a262e36c9c043a52eb09.
PR-URL: https://github.com/npm/cli/pull/527
Credit: @craigloewen-msft
Close: #527
Reviewed-by: @mikemimik
|
|
|
|
|
|
|
|
PR-URL: https://github.com/npm/cli/pull/493
Credit: @claudiahdz
Close: #493
Reviewed-by: @claudiahdz
|
|
|
|
This was broken when the support/funding functionality changed the
return value to no longer track the promise for the quick audit
printing.
It was not caught by tests, because they were only running against the
--json output, and not verifying the quick audit results in any way.
Added a test to track the --json quick audit results (which were not
broken, but someday could become so) and the human printed quick audit
results (which were broken).
Paired with @ruyadorno @mikemimik
PR-URL: https://github.com/npm/cli/pull/486
Credit: @isaacs
Close: #486
Reviewed-by: @claudiahdz
|
