Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: state that removing npm is a non-goal #51951

Merged
merged 8 commits into from
Mar 15, 2024
Prev Previous commit
Next Next commit
Update doc/contributing/technical-priorities.md
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
  • Loading branch information
GeoffreyBooth and aduh95 authored Mar 4, 2024
commit a6d9acbeb1283802257fbacc43f23a45b1ceb644
2 changes: 1 addition & 1 deletion doc/contributing/technical-priorities.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ developer experience for newcomers and experienced users alike.

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
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
Expand Down
Loading