You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See if it's possible to only need to do a single yarn install.
motivation
While the build time is dominated by webpack (and wrappers thereof), running yarn install 7 times is quite expensive.
design ideas
During env, discover all of the package.json files and build a work/package.json, and run a single yarn.
Sadly, a lot of things (in .js, .ts, .json, .toml and .py files) depend on files being deployed in a specific place in {cwd}/node_modules, so may require a lot of weird patching magic. Further, some packages run their ownyarn install inside other scripts or elsewhere.
The text was updated successfully, but these errors were encountered:
elevator pitch
See if it's possible to only need to do a single
yarn install
.motivation
While the build time is dominated by
webpack
(and wrappers thereof), runningyarn install
7 times is quite expensive.design ideas
During
env
, discover all of thepackage.json
files and build awork/package.json
, and run a singleyarn
.Sadly, a lot of things (in
.js
,.ts
,.json
,.toml
and.py
files) depend on files being deployed in a specific place in{cwd}/node_modules
, so may require a lot of weird patching magic. Further, some packages run their ownyarn
install inside otherscripts
or elsewhere.The text was updated successfully, but these errors were encountered: