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

[core] Add a script to build all packages #40631

Merged
merged 2 commits into from
Feb 22, 2024

Conversation

michaldudak
Copy link
Member

The current build script builds only the public packages (@mui/*).
This PR adds a new one, build:all to build all the workspace packages.

Alternatively, I'm also considering using build to build all packages and introducing build:public for public ones (instead of introducing build:all). This way, running build as usual will verify if the whole repo is in a buildable state.

@michaldudak michaldudak added the core Infrastructure work going on behind the scenes label Jan 16, 2024
@michaldudak michaldudak requested a review from a team January 16, 2024 10:28
@mui-bot
Copy link

mui-bot commented Jan 16, 2024

Netlify deploy preview

https://deploy-preview-40631--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 2e50d8f

@DiegoAndai
Copy link
Member

Alternatively, I'm also considering using build to build all packages and introducing build:public for public ones (instead of introducing build:all). This way, running build as usual will verify if the whole repo is in a buildable state.

Which one (all or public) would be the most commonly used? I think that one should get build

@michaldudak
Copy link
Member Author

It would be safer to build all projects (so to change the previous behavior). This way we'll ensure that all projects are in a good state all the time.

@michaldudak
Copy link
Member Author

@brijeshb42, would you mind taking a look at the failing zero-runtime-next-app build?

@brijeshb42
Copy link
Contributor

@michaldudak Yeah. I also just encountered it and am looking into the reason.

@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged label Feb 21, 2024
@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged label Feb 22, 2024
@michaldudak michaldudak merged commit 90f02bd into mui:master Feb 22, 2024
19 checks passed
@michaldudak michaldudak deleted the build-scripts branch February 22, 2024 10:38
mnajdova pushed a commit to mnajdova/material-ui that referenced this pull request Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Infrastructure work going on behind the scenes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants