The best I have is making my start script be npx yarn node app.js, but that feels unnecessarily convoluted after all, with Yarn 2, the tool itself is stored in. (And remember, we're trying to solve the problem of somebody being arbitrarily stubborn about installing things.) This happens automagically for Node instances run from Yarn scripts, but running Yarn scripts requires Yarn to be available. However, to run the actual app, Yarn needs to replace Node's dependency resolution with its PnP mechanism. (He takes umbrage at the expectation of having to run npm i on a cloned repo to make it work and insists putting node_modules into version control is somehow not a godawful idea so I want to use this as an excuse to sneak in Yarn and also stop him from powering that through.)Īs I understand, what "zero install" basically means is Yarn tries to make putting dependency installation state into VCS actually feasible. I'm playing with Yarn 2's "zero install" stuff for a minor tool to address one of my boss's random allergies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |