Scenario / test fixture: Tink

[ryan-roemer]

https://github.com/npm/tink

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).

[zkat]

You shouldn't need to do anything particularly special once tink is ready for use. Because it simulates node_modules, there's basically no real need to special-case anything: Just throw what you currently have at it and the analysis will be fairly accurate, unless you're trying to calculate the on-disk cost of the source files. If you're trying to calculate bundle sizes, though, it's all identical, or it should be. I'd rather you not have to do any extra work here! I want it to Just Work™!

[ryan-roemer]

Thanks for the comment and great to hear!!!