Scenario / test fixture: Yarn PnP

https://github.com/yarnpkg/pnp-sample-app

Should work like existing multiple-roots scenario.

Tasks:

• The abstract dependency graph is not going to be automatically inferrable because everything is or or less flat.
  • Figure out if this is an actual problem and if we should do anything about it (docs, logic, special report, etc.)
  • Investigate if there is metadata from which we could recreate the abstract dependency graph. (Probably could from yarn.lock or package-lock.json if nothing else).

[ryan-roemer]

Thanks for the comments and tips! And super looking forward to diving in and trying out PnP as a consumer on projects!!!

All in all, my intuition at a high level for this issue is that:

1. My hunch is that inspectpack (CLI and webpack plugin) will work just fine with PnP’s approach (it really should for anything with node_modules in the source path, whether in one root location or multiply across disk).
2. From the info above in this ticket, I’ll be able to create a reasonable approximation for a PnP test fixture, just won’t be able to create one that has duplicates from identical packages because that can’t happen by design 😛

[arcanis]

Yep, all that seems about right 👍