![]() Note the tilde ~ instead of the default caret ^ ![]() The above steps will add the following record in package.json: "example-package" : "~1.8.0" ![]() ![]() Note: You wouldn't do this last step if you wanted all future npm install's to use the tilde ( ~) prefix instead of a caret ( ^). a caret ( ^) by running: npm config delete save-prefix Note: The tilde ( ~) must not be included in the install command.įinally, set the save-prefix value back to it's default, i.e. Install your package by running: npm i -save Set the save-prefix value to a tilde ( ~) by running: npm config set save-prefix="~" Unfortunately, the npm install command has no option to specify this, so what you'll need to do is: The default value is a caret ( ^) which you can check by running the following npm config command: npm config get save-prefix This is good for when you don't need a very specific version, but you want to keep your dependencies up to date with the latest patches and security vulnerability fixes.įor more info, check out Caret vs Tilde in semver prefix is defined by the save-prefix config. Since we prefixed the version with ~, NPM retrieved the latest patch version under the 4.16 minor version, which turned out to be 4.16.4. So, for example, if you want to use Express version 4.16, but the patch version isn't important, you can use the tilde to tell NPM to retrieve the latest patch version: $ npm install ~4.16.1Īdded 48 packages from 36 contributors and audited 121 packages in 3.02s This way you can specify a compatible package version, but still get the latest. Using either a caret ( ^) or a tilde ( ~) we can specify the latest minor or patch version, respectively. 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 NPM, or the Node Package Manager, is a powerful tool that allows you to easily manage dependencies, run scripts, and organize project metadata. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |