NPM is planning on integrating Tink. Yarn 2 introduced PnP. The two biggest package managers in the ECMAScript ecosystem, are both starting to steer away from the node_modules directory. At least Tink is keeping the ability to “unwind” for backwards compatibility, and NPM is trying to play nice with the community (See “Play Nicer with Yarn”).

At the heart of this is “the node_modules problem”. This is a short title encompassing several pain points.

  • The size of the average node_modules directory.
  • The complexity of the node_modules filesystem.
  • That node_modules is on disk, and disk IO is slow.

Other problems are…

Chris Ackerman

Software engineer at Microsoft (Azure Identity). Veteran full stack developer and technology enthusiast.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store