Pnpm: [Question] Why you didn't just PR npm?

Created on 29 Mar 2018  路  1Comment  路  Source: pnpm/pnpm

Just curious, thanks!

question

Most helpful comment

@pierreozoux we communicate closely with the npm team but they would not use our approaches.

There are several reasons for that:

  1. pnpm uses a non-flat node_modules. Some packages rely on the flat node_modules. Even though pnpm's strictness is superior (https://medium.com/pnpm/pnpms-strictness-helps-to-avoid-silly-bugs-9a15fb306308) the switch would cause too much trouble for npm
  2. pnpm uses hard links. The npm CLI team believes that disk space is cheap and it is better to copy dependencies instead of linking them from one place.
  3. pnpm uses symlinks, so node_modules created with pnpm won't work with the --preserve-symlinks flag of Node

>All comments

@pierreozoux we communicate closely with the npm team but they would not use our approaches.

There are several reasons for that:

  1. pnpm uses a non-flat node_modules. Some packages rely on the flat node_modules. Even though pnpm's strictness is superior (https://medium.com/pnpm/pnpms-strictness-helps-to-avoid-silly-bugs-9a15fb306308) the switch would cause too much trouble for npm
  2. pnpm uses hard links. The npm CLI team believes that disk space is cheap and it is better to copy dependencies instead of linking them from one place.
  3. pnpm uses symlinks, so node_modules created with pnpm won't work with the --preserve-symlinks flag of Node
Was this page helpful?
0 / 5 - 0 ratings