From 8824adb031afa0d0c40a9757ea8c9c5ff8c52281 Mon Sep 17 00:00:00 2001 From: Geoffrey Booth Date: Thu, 14 Mar 2024 17:47:26 -0700 Subject: [PATCH] doc: state that removing npm is a non-goal PR-URL: https://github.com/nodejs/node/pull/51951 Reviewed-By: Matteo Collina Reviewed-By: Yagiz Nizipli Reviewed-By: Robert Nagy Reviewed-By: Luigi Pinca Reviewed-By: Antoine du Hamel Reviewed-By: Luke Karrys Reviewed-By: Marco Ippolito Reviewed-By: Richard Lau Reviewed-By: Myles Borins Reviewed-By: Chengzhong Wu Reviewed-By: Moshe Atlow Reviewed-By: Ethan Arrowood Reviewed-By: Ruy Adorno Reviewed-By: Michael Dawson --- doc/contributing/technical-priorities.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/contributing/technical-priorities.md b/doc/contributing/technical-priorities.md index c2576edad4d03a..a11ae0e556987f 100644 --- a/doc/contributing/technical-priorities.md +++ b/doc/contributing/technical-priorities.md @@ -160,3 +160,18 @@ and integration with other systems. As TypeScript usage continues to grow and gains more prominence in the ecosystem, enhancing its support is essential for delivering an improved developer experience for newcomers and experienced users alike. + +## Package management + +The ability to easily install and manage dependencies and development tools is a +key part of the user experience, and for that reason Node.js must provide a +package manager as part of its distribution. Node.js includes `npm` for this +purpose. This is for historical reasons — when `npm` was added in 2011, it was +the only JavaScript package manager — and because it is the reference +implementation for the npm registry, which is the de facto primary source for +most JavaScript software. In accordance with our [policy][distribution-policy] +of not including multiple dependencies or tools that serve the same purpose, the +Node.js project does not include any other package managers; though it may +include other software to download other package managers. + +[distribution-policy]: ./distribution.md