While you are welcome to explore JavaScript packages further on your own, you are expected to use the pinned versions for independent projects.

As stated in the last lesson, companies generally do not automatically upgrade to latest releases, especially if the version they are already using is reliable and they don't need any new features that more recent versions offer. Version pinning is commonly used throughout the industry. The latter is a recipe for breaking our code - and a very frustrating debugging situation. This is exactly what we were talking about in the last lesson! For that reason, it's more important to create a stable environment where all packages work together instead of a potentially chaotic environment where we are always installing the latest version of a package without fully testing whether it works with other packages we're using. When a package is updated, it won't necessarily play nicely with all the other packages in our environment. Most of the packages we'll install specify a version of the package.

Using the npm install to direct npm to install packages listed in a package.json file.Īs you work through this lesson, make sure you actually install the two packages to your Shape Tracker project: webpack and webpack-cli.

The difference between dependencies and devDependencies.

We can install any npm package with the $ npm install command where is the package we want to install.Īs we learn how to use npm to install packages, we'll also learn about:

We're now ready to start installing the packages we'll work with.

Howto install npm