With NPM we also have other options for specifying the version of a package.

To do this, we can specify the version using the syntax npm install Continuing with our example above, we would execute something like this: $ npm install Īdded 48 packages from 36 contributors and audited 121 packages in 2.986sĪs you can see, NPM has installed the package we specified. In cases like this you'd probably want to install a specific version of the package that you know works, or that you know is 'safe'. When you run the install command like this, by default it retrieves the latest version of the specified package, which in this case is v4.17.1 (at the time of this writing).īut what if we need a different version? Maybe this latest version breaks a feature that we need, or maybe it has a security vulnerability that the maintainer hasn't gotten around to fixing yet. It's main purpose, however is to help you download and install Node packages from its repository to your project.ĭownloading and installing a package is done using NPM's install command: $ npm install expressĪdded 50 packages from 37 contributors and audited 126 packages in 3.262s How is a dependency specified in package.json by default?įirst, what happens when you npm install something? npm install default, it saves the package as a dependency in your project’s package.NPM, or the Node Package Manager, is a powerful tool that allows you to easily manage dependencies, run scripts, and organize project metadata. The precursor to the v1.0 release – v0.11.0 – was published recently.Īs I was on v0.10.0, the latest update should have been simple to upgrade to, right? Just using the update option on npm and specifying the package should have done, like so: npm upgrade turns out, this didn’t work! 😭 It is, therefore, implicitly signalled by the developer to not be ready for production.

I use Eleventy, and it hasn’t hit v1.0 yet.

If you don’t want to waste a full hour like I did, this might be helpful.

If you subscribe to the philosophy of Semantic Versioning (you should!) and use npm, there is a certain behaviour that might trip you up. How is a dependency specified in package.json by default?.

Update npm package to latest