The npm blog has been discontinued.
npm v4.4.3 released
Trying something new…
We’re going to start publishing our changelogs over here on the npmjs blog. Today we have for you v4.4.3 from myself (@iarna) and v4.4.2 from Kat (@zkat).
This is a small patch release, mostly because the published tarball for v4.4.2 was missing a couple of modules, due to a bug involving scoped modules, bundled dependencies and legacy tree layouts.
There are a couple of other things here that happened to be ready to go. So without further ado…
email@example.com: Make sure we never, ever remove home directories. Previously if your home directory was entirely empty then we might
1af85ca9f#16040 Fix bug where bundled transitive dependencies that happened to be installed under bundled scoped dependencies wouldn’t be included in the tarball when building a package. (@iarna)
13c7fdc2e#16040 Fix a bug where bundled scoped dependencies couldn’t be extracted. (@iarna)
d6cde98c2#16040 Stop printing
ENOENTerrors more than once. (@iarna)
722fbf0f6#16040 Rewrite the
extractaction for greater clarity. Specifically, this involves moving things around structurally to do the same thing
d0c6d194did, but in a more comprehensive manner. This also fixes a long standing bug where errors from the move step would be eaten during this phase and as a result we would get mysterious crashes in the finalize phase when finalize tried to act on them. (@iarna)
6754dabb6#16040 Flatten out
@npmcorp/move’s deps for backwards compatibility reasons. Versions prior to this one will fail to install any package that bundles a scoped dependency. This was responsible for
ENOENTerrors during the
This week, the focus on the release was mainly going through all of npm’s deps that we manage ourselves, and making sure all their PRs and versions were up to date. That means there’s a few fixes here and there. Nothing too big codewise, though.
The most exciting part of this release is probably our shiny new Contributing and Troubleshooting docs! @snopeks did some ✨fantastic✨ work hashing it out, and we’re really hoping this is a nice big step towards making contributing to npm easier. The troubleshooting doc will also hopefully solve common issues for people! Do you think something is missing from it? File a PR and we’ll add it! The current document is just a baseline for further editing and additions.
Also there’s maybe a bit of an easter egg in this release. ‘Cause those are fun and I’m a huge nerd. 😉
CONTRIBUTING.mdand add new
TROUBLESHOOTING.mdfiles. 🙌🏼 (@snopeks)
2f3e4b6#15833 Mention the 24-hour unpublish policy on the main registry. (@carols10cents)
NOT REALLY FEATURES, NOT REALLY BUGFIXES. MORE LIKE TWEAKS? 🤔
84be534#15888 Stop flattening
ls-tree output. From now on, deduped deps will be marked as such in the place where they would’ve been before getting hoisted by the installer. (@iarna)
e9a5dca#15967 Limit metadata fetches to 10 concurrent requests. (@iarna)
46aa9bc#15967 Limit concurrent installer actions to 10. (@iarna)
c3b994b#15901 Use EXDEV aware move instead of rename. This will allow moving across devices and moving when filesystems don’t support renaming directories full of files. It might make folks using Docker a bit happier. (@iarna)
0de1a9c#15735 Autocomplete support for npm scripts with
:colons in the name. (@beyondcompute)
84b0b92#15874 Stop using undocumented
895ffe4#15824 Fix empty versions column in
npm searchoutput. (@bcoe)
firstname.lastname@example.org: npm/init-package-json#61 Exclude existing
devDependenciesfrom being added to
dependencies. Fixes #12260. (@addaleax)