pnpm v9

[zkochan]

This is a discussion about pnpm v9 breaking changes.

• remove the ability to automatically convert lockfile v5 to v6
• link-workspace-packages should be false by default. So, only packages specified with the workspace: protocol will be linked from the workspace. This behaviour is less confusing then linking all dependencies. feat!: link-workspace-packages is false by default #7485
• set dedupe-injected-deps to true by default (related PR feat: dedupe injected dependencies #7416).
• set hoist-workspace-packages to `true by default (related PR feat: add hoist-workspace-packages option #7451)
• pnpm setup should not use the Library directory on mac #7321
• throw an error when resolutions or pnpm field are used in a non-root workspace project (now a warning is printed fix: should output warning info when "pnpm" or "resolutions" is configured in a non-root workspace project #6658)
• make the path to the CAFS shorter (remove the files subdirectory from the path). It should reduce the amount of times these errors happen: pnpm install ENAMETOOLONG #2605
• move the default location of the virtual store from node_modules/.pnpm to .pnpm in order to reduce issues like this: Flattening feature creates lengthy folder structures #6830 People voted against it: https://twitter.com/pnpmjs/status/1739962479097122843
• the requiresBuild field should either be removed from the lockfile or be included always, regardless if the dependency is allowed to be built or not (related PR feat: onlyBuiltDependenciesFile #7167)
• patchedDependencies in the lockfile should not contain paths. It is enough to just store their hashes
• implement Apply publishConfig for workspace packages on deployment #6693 again as a breaking change
• improve the way side-effects cache is saved in index files.
• don't remove node_modules when registry configuration changes

Related PR: #7459

[Mister-Hope]

It would be great if someone can pick #4982.

Examples in node docs are already using node: for core modules (e.g.: https://nodejs.org/docs/latest/api/synopsis.html), while this behavior is broken since the options is added.

I tried to raise the pr but I am not be able to find the related codes in the codebase, seems that when getting builtinModules via node:module, we also need to manually check the ones with node: prefix