Releases: npm/npm
1.3.26
1.3.25
1.3.24
Make the search output prettier, with nice truncated columns, and a --long
option to create wrapping columns. (20439b2 and 3a6942d, @timoxley)
Support multiple packagenames in npm docs
. (823010b, @timoxley)
Fix the npm adduser
bug regarding "Error: default value must be string or number" again. (b9b4248, @isaacs)
Fix scripts
entries containing whitespaces on Windows. (80282ed, @robertkowalski)
Fix npm update
for Git URLs that have credentials in them (93fc364, @danielsantiago)
Fix npm install
overwriting npm link
-ed dependencies when they are tagged Git dependencies. (af9bbd9, @evanlucas)
Remove npm prune --production
since it buggily removed some dependencies that were necessary for production; see #4509. Hopefully it can make its triumphant return, one day. (1101b6a, @isaacs)
Dependency updates:
1.3.23
1.3.22
Fix a critical bug in npm adduser
that would manifest in the error message "Error: default value must be string or number." (fba4bd2, @isaacs)
Allow npm bugs
in the current directory to open the current package's bugs URL. (d04cf64, @evanlucas)
Several fixes to various error messages to include more useful or updated information. (1e6f2a7, ff46366, 8b4bb48; @rlidwka, @evanlucas)
1.3.21
Fix a critical bug that prevented publishing due to incorrect hash calculation. (npm/npm-registry-client@4ca4a2c, @dominictarr)
v1.3.20
v1.3.19
1.3.18
Added an --ignore-scripts
option, which will prevent package.json
scripts from being run. Most notably, this will work on npm install
, so e.g. npm install --ignore-scripts
will not run preinstall and prepublish scripts. (d7e67bf, @sqs)
Fixed a bug introduced in 1.3.16 that would manifest with certain cache configurations, by causing spurious errors saying "Adding a cache directory to the cache will make the world implode." (966373f, @domenic)
Re-fixed the multiple download of URL dependencies, whose fix was reverted in 1.3.17. (a362c3f, @spmason)
1.3.17
This release reverts 644c2ff, which avoided re-downloading URL and shinkwrap dependencies when doing npm install
. You can see the in-depth reasoning in d8c907e; the problem was, that the patch changed the behavior of npm install -f
to reinstall all dependencies.
A new version of the no-re-downloading fix has been submitted as #4303 and will hopefully be included in the next release.