4 ms·
In addition to Yarn PnP, the folks at npm are still working on tink[0] which is early but useable right now. [0]: https://blog.npmjs.org/post/178027064160/next
by sisk 8y ago
In addition to Yarn PnP, the folks at npm are still working on tink[0] which is early but useable right now.
[0]: https://blog.npmjs.org/post/178027064160/next-generation-package-management https://blog.npmjs.org/post/178027064160/next-generation-pac...
- acemarke 8y agoYep. I've glanced briefly at both PnP and Tink. Both sound neat conceptually, I just haven't dug far enough to know what the differences are in terms of actual approaches and implementation. Also haven't had a chance to play with either yet. Long-term, stuff like the size of `node_modules` seems very solvable. Simultaneously with that, I do think that there'd be benefit if some of the larger JS build tools started evaluating their own transitive dependencies and submitting PRs to inline some of the smaller pieces somehow [0]. [0] https://twitter.com/acemarke/status/1073593305378754560 https://twitter.com/acemarke/status/1073593305378754560
- swsieber 8y agoUnfortunately, the ts compiler neither supports yarn pnp or rink right (and angular doesn't either). It's the biggest blocker for me personally - but I've played with yarn pnp and it's great.