4 ms·
Very cool, does this mean you can check in the dependency file to version control? Just like yarn.lock? As much as I hate node_modules, there are times when I
by gitgud 8y ago
Very cool, does this mean you can check in the dependency file to version control? Just like yarn.lock?
As much as I hate node_modules, there are times when I want to see how a library is implemented. Is there a way to have some libraries in node_modules? Say only the ones in listed in the package.json file
- ndarilek 8y agoSecond this. I'd ask that any dependencies in node_modules/ override whatever is cached. For a work project, I'm updating a dependency written against an undocumented specification. Much fun is being had doing this, I assure you. Being able to crack open the sources in node_modules/, instrument things with logging, and fix fix fix until I get something working is very helpful. I'm sure I can track things down in a cache directory and do the same, but it's nice knowing that my changes are limited to just this particular project, and that a checkout/reinstall of the module in another project will get the original broken sources for comparison.
- arcatek 8y agoThe .pnp.js file can be checked-in, but needs the cache to work. Right now I'd advise not to check-it in. `yarn unplug` will eject a dependency from the cache and put it into the project folder. That's a quick and easy way to inspect and debug libraries you use.
- w4tson 8y agoJust curious, why not?
- arcatek 8y agoIt doesn't have a lot of advantages right now. That said, it won't stay true forever. PnP is but the first step of a long-term goal I have. Check the Section 6.B from the whitepaper[1] for more details. [1] https://github.com/yarnpkg/rfcs/blob/65b36475c04b1149eb51a81875bad9b853e113fb/accepted/0000-plug-an-play.md#b-tarball-unpacking https://github.com/yarnpkg/rfcs/blob/65b36475c04b1149eb51a81...