| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This removes a lot of very outdated dependencies, updates many to
their modern (usually promisified) versions, and updates (or removes)
code to account for the change.
Several dependencies have been completely removed, and others a bit
shuffled around, so that the node_modules folder can be bundled somewhat
more optimally than it would have otherwise.
|
|
- Several sections of code moved out into separate modules.
- npm is an instance of an inline class.
- uses a Proxy for npm.commands object instead of the old hand-rolled
Proxy-esque thing.
- organized code path for outputting usage/help information.
|
|
Suggested by @godmar in
https://npm.community/t/npm-err-cb-never-called-permission-denied/9167/5
Incidentally, this turned up that we're catching uncaughtExceptions in
the main npm functions, but not unhandledRejections!
Tracing this through, it seems like node-fetch-npm's use of cacache is
particularly brittle. Any throw that comes from cacache is not caught
properly, since node-fetch-npm is all streams and callbacks. The naive
approach (just adding a catch and failing the callback) doesn't work,
because then make-fetch-happen and npm-registry-fetch interpret the
failure as an invalid response, when actually it was a local cache
error.
So, a bit more love and polish is definitely still needed in the
guts of npm's fetching and caching code paths. In the meantime, though,
handling any unhandledRejection at the top level prevents at least the
worst and most useless type of error message.
PR-URL: https://github.com/npm/cli/pull/227
Credit: @isaacs
Close: #227
Reviewed-by: @isaacs
|
|
PR-URL: https://github.com/npm/cli/pull/138
Credit: @elidoran
Reviewed-By: @aeschright
|
|
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
|
|
|
|
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
|
|
PR-URL: https://github.com/npm/npm/pull/9954
|
|
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
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
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
|
|
|
|
|
