diff --git a/packages/learn/src/introductions/apis-and-microservices/managing-packages-with-npm/index.md b/packages/learn/src/introductions/apis-and-microservices/managing-packages-with-npm/index.md index 7507a8ef5a..babd0401be 100644 --- a/packages/learn/src/introductions/apis-and-microservices/managing-packages-with-npm/index.md +++ b/packages/learn/src/introductions/apis-and-microservices/managing-packages-with-npm/index.md @@ -5,6 +5,6 @@ superBlock: APIs and Microservices --- ## Introduction to the Managing Packages with npm Challenges -The Node Package Manager (npm) is a command-line tool used by developers to share and control modules (or packages) of JavaScript code written for use with Node.js.

When starting a new project, npm generates a package.json file. This file lists the package dependencies for your project. Since npm packages are regularly updated, the package.json file allows you to set specific version numbers for each dependency. This ensures that updates to a package don't break your project.

npm saves packages in a folder named node_modules. These packages can be installed in two ways:

  1. globally in a root node_modules folder, accessible by all projects.
  2. locally within a project's own node_modules folder, accessible only to that project.

Most developers prefer to install packages local to each project to create a separation between the dependencies of different projects. +The Node Package Manager (npm) is a command-line tool used by developers to share and control modules (or packages) of JavaScript code written for use with Node.js.

When starting a new project, npm generates a package.json file. This file lists the package dependencies for your project. Since npm packages are regularly updated, the package.json file allows you to set specific version numbers for each dependency. This ensures that updates to a package don't break your project.

npm saves packages in a folder named node\_modules. These packages can be installed in two ways:

  1. globally in a root node\_modules folder, accessible by all projects.
  2. locally within a project's own node\_modules folder, accessible only to that project.

Most developers prefer to install packages local to each project to create a separation between the dependencies of different projects. Working on these challenges will involve you writing your code on Glitch on our starter project. After completing each challenge you can copy your public Glitch url (to the homepage of your app) into the challenge screen to test it! Optionally you may choose to write your project on another platform but it must be publicly visible for our testing.
Start this project on Glitch using this link or clone this repository on GitHub! If you use Glitch, remember to save the link to your project somewhere safe!