The npm blog has been discontinued.
npm Weekly, #5
Here’s your weekly serving of the choicest npm updates. Would you like to have them delivered to you directly?
What’s new in the CLI
You might notice a few new warnings when you update to
We’re removing the engineStrict key from package.json in
npm@3, so you’ll start seeeing warnings about this change in
firstname.lastname@example.org. You’ll still be able to set the engine for your environment in your
.npmrc, but allowing packages to set engine requirements never quite worked out right for users, so that’s what we’re taking out.
We will also be changing the behavior of
npm@3. We won’t be automatically downloading the peer dependency anymore. Instead, we’ll warn you if the peer dependency isn’t already installed. This requires you to resolve peerDependency conflicts yourself, manually, but in the long run this should make it less likely that you’ll end up in a tricky spot with your packages’ dependencies.
What’s coming in npm@3
With npm@3, your
node_modules directory will be a lot flatter. All of your dependencies and most of your subdependencies (and (sub)+dependencies) will be sitting next to each other at the top level. Only when there are conflicts will modules be installed at deeper levels. This should make things a lot easier for Windows users.
How to npm
npm has a new interactive workshop, how-to-npm. Learn how to publish packages to npm, update them, and do other maintanence-y tasks. And don’t worry, it won’t publish anything to the public registry, only to a mock registry on your own machine.