| Age | Commit message (Collapse) | Author |
|---|
|
PR-URL: https://github.com/npm/cli/pull/33
Credit: @Sibiraj-S
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/32
Credit: @olore
Reviewed-By: @zkat
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/20750
Credit: @travi
Reviewed By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/20536
Credit: @zkat
Reviewed-By: @iarna
|
|
This message is based on the one pnpm uses, which
I think takes care of all the false update messages and
missing -g that happens with the default notifier message.
It also tells people what "level" the update is.
Credit: @zkat
PR-URL: https://github.com/npm/npm/pull/20122
Reviewed-By: @iarna
|
|
PR-URL: https://github.com/npm/npm/pull/20214
Credit: @zkat
|
|
|
|
It was incorrectly calling `node npx-cli prefix` which led to downloading "prefix" package.
Instead it should be calling `node npm-cli prefix`
PR-URL: https://github.com/npm/npm/pull/19608
Credit: @laggingreflex
Reviewed-By: @zkat
|
|
The script isn't called, isn't made available as a binary.
Credit: @metux
Reviewed-By: @iarna
PR-URL: https://github.com/npm/npm/pull/16547
|
|
npx is an npm package runner with a bunch of nice features. While
it is also available on the npm registry as `npx`, it's the sort
of thing that's better off being bundles with npm itself.
Fixes: #6053
PR-URL: https://github.com/npm/npm/pull/17685
Credit: @zkat
Reviewed-By: @iarna
|
|
Credit: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/16750
Credit: @aredridel
Reviewed-By: @zkat
|
|
* Don't ham-it-up when expecting JSON
I turned on the ham-it-up configuration setting, and then noticed that I received an error when running the npm-windows-upgrade module, because it was trying to parse the JSON from calling `npm view npm versions --json` and didn't know what to do with the easter egg text at the end.
This change disables the ham-it-up text when the json option is present.
PR-URL: https://github.com/npm/npm/pull/16336
Credit: @bdukes
Reviewed-By: @zkat
|
|
|
|
This will allow moving across devices and moving when filesystems don't
support renaming directories full of files.
PR-URL: https://github.com/npm/npm/pull/15901
Credit: @iarna
Reviewed-By: @zkat
|
|
Fixes: #15855
PR-URL: https://github.com/npm/npm/pull/15864
Credit: @legodude17
Reviewed-By: @iarna
|
|
The cli bin script now runs the update-notifier module after
it has decided we're running in a good node version. We do not
yet customize the output in any way.
Credit: @ceejbot
Fixes: #11473
PR-URL: https://github.com/npm/npm/pull/15774#pullrequestreview-23599057
Reviewed-By: @iarna
|
|
Also error on really old versions where we know we can't work.
Credit: @iarna
Reviewed-By: @othiym23
Reviewed-By: @zkat
PR-URL: https://github.com/npm/npm/pull/14230
|
|
Credit: @othiym23
PR-URL: https://github.com/npm/npm/pull/11444
Reviewed-By: @zkat
Reviewed-By: @iarna
Reviewed-By: @othiym23
|
|
Existing behavior invoking npm within a Git Bash session is to prefer
the globally installed instance of `npm`; the instance of npm installed
alongside Node when using the Node installer.
The cmd script, and the shell script, have been modified in the past to
pull a `prefix` setting from the global `npmrc` file, and invoke the
`npm` instance located at the `prefix` location. Because the value of
`prefix` is the user's AppData directory where npm installs new copies
of itself, the user gets the latest installed npm.
However, the setup was not extended to support Git Bash. Therefore Git
Bash users still get the version of npm installed beside Node.
Add support for using the same prefix for invoking the user installed
npm in Git Bash sessions.
PR-URL: https://github.com/npm/npm/pull/11526
Credit: @destroyerofbuilds
Reviewed-By: @iarna
Fixes: #11524
|
|
npm sets node_config_node_gyp without quotes, so its usage should be
quoted. Indeed, it is a better practice to define environment variables
that contain paths without quotes and quote their usage.
PR-URL: https://github.com/npm/npm/pull/11158
Credit: @orangemocha
Reviewed-By: @othiym23
|
|
PR-URL: https://github.com/npm/npm/pull/9954
|
|
This changes npm.cmd and the npm script when running in Cygwin to look
for an npm installation in prefix, running it if found. The default npm
is used to get the prefix. This implements the changes described in
https://github.com/joyent/node/issues/8528 .
Fixes joyent/node#8528. Reference: joyent/node#8554.
Fixes: #6412
PR-URL: https://github.com/npm/npm/pull/9089
|
|
PR-URL: https://github.com/npm/npm/pull/9037
Fixes: https://github.com/npm/npm/issues/8704
|
|
This is a huge set of mostly mechanical changes. Going forward, all
changes to the npm source base are expected to comply with `standard`,
and it's been integrated into the test suite to enforce that. There are
a few notes below about specific classes of changes that need to be
handled specially for npm's code base.
standard: "Expected error to be handled."
`standard` only expects errors spelled "err" to be handled.
`npm-registry-mock` never actually invokes its callback with an error,
so in some cases I just changed it to be spelled "er" and called it
good.
standard: "Expected a "break" statement before 'case'."
This behavior is actually on purpose, and I don't feel like rewriting
the affected code right now (or, you know, ever). So I added code
comments disabling the checks in the three applicable changes.
standard: "x is a function."
Rebinding functions created via declarations (as opposed to expressions)
is a no-no?
PR-URL: https://github.com/npm/npm/pull/8668
|
|
commands
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/8324
|
|
Enable overriding the node-gyp binary used by npm by specifying
a config option, similar to specifying the python interpreter.
Example usage:
npm install --node-gyp=<path-to-custom-node-gyp>
|
|
|
|
|
|
Node v0.6 is pretty much gone at this point. Also, the -pre upsets
SemVer 4, making it annoying to test npm on Node in development.
|
|
make sure that npm script runs on cygwin platform even when installed in DOS encoding
cf. http://sourceware.org/ml/cygwin-announce/2009-07/msg00002.html (option 4a)
|
|
|
|
|
|
|
|
|
|
This feels so good. lib/utils/log.js is the worst kind of
glue code that keeps the npm project from being properly
abstracted into independent pieces.
In the process, also cleaned up a lot of unproductive logging,
and made the npm-debug.log generated on errors be a bit more
easy to read.
|
|
|
|
|
|
For @mcavage
|
|
|
|
Unnecessary and unportable
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
lib/utils/mkdir-p.js
lib/utils/output.js
|
