| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent b360532 commit 8824adb
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -160,3 +160,18 @@ and integration with other systems. | |||
| 160 | 160 | As TypeScript usage continues to grow and gains more prominence in the | |
| 161 | 161 | ecosystem, enhancing its support is essential for delivering an improved | |
| 162 | 162 | developer experience for newcomers and experienced users alike. | |
| 163 | + | ||
| 164 | + ## Package management | ||
| 165 | + | ||
| 166 | + The ability to easily install and manage dependencies and development tools is a | ||
| 167 | + key part of the user experience, and for that reason Node.js must provide a | ||
| 168 | + package manager as part of its distribution. Node.js includes `npm` for this | ||
| 169 | + purpose. This is for historical reasons — when `npm` was added in 2011, it was | ||
| 170 | + the only JavaScript package manager — and because it is the reference | ||
| 171 | + implementation for the npm registry, which is the de facto primary source for | ||
| 172 | + most JavaScript software. In accordance with our [policy][distribution-policy] | ||
| 173 | + of not including multiple dependencies or tools that serve the same purpose, the | ||
| 174 | + Node.js project does not include any other package managers; though it may | ||
| 175 | + include other software to download other package managers. | ||
| 176 | + | ||
| 177 | + [distribution-policy]: ./distribution.md | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments