Whether to use -save-dev or not depends on your use cases. # or specific version npm install -save-dev tip To install the latest release or a specific version, run one of the following commands: npm install -save-dev webpack You may run into a variety of issues with the older versions as they may be missing functionality webpack and/or its related packages require. The current Long Term Support (LTS) release is an ideal starting point. Prerequisitesīefore we begin, make sure you have a fresh version of Node.js installed. Running lerna exec - npm update ava nyc esm take way too long and moreover actually install the package when I just want to update the package.json.Ĭopy-pasting the version to all package.json and running lerna bootstrap -hoist is viable, but as the number of sub-packages grows it becomes more and more tedious.This guide goes through the various methods used to install webpack. Updating these dependencies can turn into a nightmare.

It means I can run npm test in the root to test everything (in CI for example) or in any sub-directory (while adding a new feature for example). Have a lot of sub-packages with outdated dependenciesĪll my sub-packages and root share AVA, nyc and esm.Possible SolutionĪ command like lerna update could run over every package.json and match the version with the root.Īlternatively, in order to not rely in the root package, lerna update could be used to define the required version. Of course I can use lerna exec - npm update whatever, but NPM will actually install the new version in each packages which can take forever. However, when updating shared dependencies offer no help to bump version in all packages. Lerna is able to hoist shared dependencies to the top (which is nice). This mean all packages (including root) share the same test runner. For example, it's nice to be able to run tests in a specific package and at the root directory. DevDependencies can be shared amongst the root package and sub-packages.

Npm update package to specific version