Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions doc/contributing/technical-priorities.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

## Non-goals
Comment thread
GeoffreyBooth marked this conversation as resolved.
Outdated

The following are not considered technical priorities for the project:

* **Unbundling `npm`**. When `npm` was included in the Node.js distribution, it
was the only JavaScript package manager available, and it was provided as a
way to help developers easily install other JavaScript software. `npm` is also
the reference implementation for the `npm` registry, which is the de facto
Comment thread
GeoffreyBooth marked this conversation as resolved.
Outdated
primary source for most JavaScript software. Today, `npm` is one of many
high-quality options. However, the potential removal of `npm` would be a very
disruptive breaking change, even as a semver-major change, and therefore it is
not a goal of the Node.js project to work toward such a goal. The `npm`
library included with the Node.js distribution can be freely used as a
dependency of other parts of the Node.js distribution.
Comment thread
GeoffreyBooth marked this conversation as resolved.
Outdated