Make @angular-devkit/core/node/resolve independent of node_modules resolution

[bgotink]

🚀 Feature request

Description

The custom resolution provided by @angular-devkit/core/node/resolve reimplements the node_module resolution algorithm, which doesn't work for package manages that don't use node_modules (yarn 2 with plug'n'play, npm tink if that gets revived).

Describe the solution you'd like

Replace the custom node_modules implementation with calls to either require.resolve with the paths option or to a require function created using createRequire.
These functions work regardless of the used package manager (yarn 1, yarn 2 with pnp, npm, pnpm, …)

Describe alternatives you've considered

• Override the resolution, using either
  • setResolveHook
  • a patch applied to the @angular-devkit/core package via yarn 2's patch protocol or via a yarn plugin
• Explicitly query the yarn PnP API, but that would require plug'n'play-specific logic in the resolution file.

[clydin]

That code is currently deprecated and unused by the CLI. Based on the deprecation process, it should be eligible for removal by the next major release.

However, I would like to thank you for taking the time to investigate Yarn 2.0 support. Contributions are always appreciated.

[bgotink]

I did some digging and it turns out I had one dependency still on version 0.803, updating that to 0.900 fixed it the issues.
Thanks!

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}