![]() ![]() While Yarn does its best to guarantee that what works now will keep working, there's always the off chance that a future Yarn release will introduce a bug that will prevent you from installing your project. ![]() The main way it does this is through a lockfile, which contains all the information needed for a project to be installed in a reproducible way across systems. Yarn does its best to guarantee that running yarn install twice will give you the same result in both cases. What does this do to my repository size?.Is it different from just checking-in the node_modules folder?.How do you reach this "zero-install" state you're advocating for? How does Yarn impact a project's stability? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |