AI summary by TwinMind
Node And NPM Are Breaking Up? NodeJS TSC Has Important Conversation
Theo - t3․gg
30m 55s
Background and Context
- JS Community debate intensifies over enabling Corepack by default and potentially unbundling npm
- Video creator had recorded content previously but chose not to publish due to rapidly changing situation
- Discussion with Yagiz (Node.js contributor, performance expert) who built Corepack to reduce package manager dependency concerns
- Current state: Node.js ships with npm by default, creating semi-necessary dependency and limiting fair opportunity for alternatives
Corepack Overview and Current Issues
- Corepack allows running commands that check package.json for specified package manager and installs if needed
- Not default because npm is default - handful of Node TSC members pushing to unbundle
- Corepack distributed by default with recent Node versions but developers must run
corepack enableto install yarn/pnpm binaries - Package manager field in package.json does nothing without manually enabling Corepack first
Socket Blog Post Analysis (by Sarah)
- Heated debate over proposal to enable Corepack by default (opened November last year)
- Sparked question of npm distribution through Corepack moving forward
- Some contributors believe eventual goal is uncoupling Node releases from npm releases
- Proponents argue: streamlines development experience, simplifies version management, creates level playing field for alternative package managers
npm's Opposition Position
- Miles Borens (npm representative) firmly opposes distribution through Corepack
- Exact quote: "npm does not wish to integrate for variety of reasons and we don't want to be forced into supporting this pattern"
- Requests if Corepack enabled by default, npm support should remain behind additional opt-in flag
- Suggests developers wanting Corepack flow should choose different package manager (yarn)
Technical Issues Raised by npm Team
- Jumper pattern introduces extra indirection, lack of clarity on package manager version/location
- Pinning package manager at project level leads to security vulnerability exposure
- Lack of clear testing between Node and package manager versions
- Hard-coded version for package managers in Corepack adds additional update labor
- Must dynamically install package manager over network to start using Node project
- Lack of clear benefit to npm while creating additional work
Video Creator's Counterarguments
- Disagrees with npm's security vulnerability argument - same applies to pinning Node versions
- Points out npm security updates require Node upgrades, which is problematic
- Non-npm users forced to worry about npm vulnerabilities they don't use
- Argues current tight coupling between npm and Node creates vulnerabilities
TSC Member Positions
Yagiz (Vocal Proponent)
- Recommends either removing npm or bundling additional package managers
- Argues ambiguity creates unnecessary friction
- Believes without Corepack, no path to removing npm as Node binary dependency
Matteo Collina (Opposition)
- "Success of Node is success of npm - don't break the magic combo"
- Shipping package manager by default key factor for Node's flourishing success
- No good technical reason to migrate npm out
- Stability of build advantage - clear npm version tied to Node version
- Corepack creates "time bomb for maintainers" due to unclear builds
Other TSC Perspectives
- Concern about Corepack usage levels - many developers don't know what it is
- Committee agreed they lack full understanding of proposed change impact
- 60% of surveyed developers don't know what Corepack is, 20% know, 20% "kind of"
Community Feedback Examples
- Hard Fist filed template issue - developers forget to enable Corepack, making package manager field non-functional
- pnpm community uses "engines" key instead due to Corepack not being default
- Next.js Docker example required adding
corepack enablecommand to work properly - Community member noted yarn v1 responsible for 25% of registry traffic
Isaac Schlueter's (npm Creator) Position
- Not Node's job to make level playing field
- Corepack doesn't solve problems other than fairness (which shouldn't be Node's problem)
- Package manager key usefulness not sufficient justification
- Argues against "perfect solution fallacy" - Corepack isn't perfect, won't be for while
- Emphasizes Node should care about Node user success, not package manager market fairness
Steven Sewell's Contribution
- Vercel employee with deep ecosystem knowledge
- Points out Corepack solves problem of choosing right package manager, not just anti-competitive issues
- This aspect getting overlooked in discussions focused on monopoly concerns
Decision Process and Timeline
- Matter too contentious for consensus - will go to vote
- Three separate questions identified:
- Goal to remove npm from Node? (yes/no)
- If not removing npm, should Corepack be included? (yes/no)
- Should Corepack be enabled by default today? (yes/no)
- Jeffrey suggests earliest action would be April
- Multiple stakeholders need to organize thoughts and PRs addressing Node's technical priorities
- Topic hasn't been on agenda for recent meetings
Technical Considerations and Alternatives
- Vendoring yarn/pnpm into Node like npm considered unrealistic
- Would introduce security issues, bundle size problems
- Wouldn't fit well with lifetime support policy
- Discussion of formalizing Node's relationship with package managers needed
Historical Context
- Isaac clarifies no "shady back room deal" for npm bundling
- Ryan Dahl and Isaac saw users constantly hitting barriers without package manager
- npm was obvious choice - no alternatives at time, supported by core Node team member
- Ryan Dahl has regrets about npm integration, package.json design
- Deno built as response to perceived npm/Node integration failures
Ecosystem Impact Assessment
- Need to substantiate major changes due to long-term ecosystem impact
- Development workflow could be forever altered
- May not foster same level of innovation and community engagement
- Question of how new package managers would get added to Corepack
- Concern about including competing runtimes like Bun
Recognition of npm's Contribution
- npm described as "one of best package management solutions of all time"
- Groundbreaking generational leap in dependency management quality
- Comparison to Python's pip shows npm's relative excellence
- Acknowledgment that npm team has given ecosystem a gift despite controversies
