Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate single yarn workspace #25

Open
bollwyvl opened this issue Dec 13, 2023 · 0 comments
Open

Investigate single yarn workspace #25

bollwyvl opened this issue Dec 13, 2023 · 0 comments
Labels
enhancement New feature or request performance Affects the wall-clock time of building a PR

Comments

@bollwyvl
Copy link
Contributor

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), 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 own yarn install inside other scripts or elsewhere.

@bollwyvl bollwyvl added enhancement New feature or request performance Affects the wall-clock time of building a PR labels Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request performance Affects the wall-clock time of building a PR
Projects
None yet
Development

No branches or pull requests

1 participant