-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[utils] Convert all exports to modules #39882
[utils] Convert all exports to modules #39882
Conversation
Netlify deploy previewhttps://deploy-preview-39882--material-ui.netlify.app/ @material-ui/lab: parsed: -0.41% 😍, gzip: -0.33% 😍 Bundle size reportDetails of bundle changes (Toolpad) |
I've tried re-running the whole CI but |
This would fix #40434 (comment) |
…s/convert-everything-to-module
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…s/convert-everything-to-module
…s/convert-everything-to-module
"build:node": "node ../../scripts/build.mjs node", | ||
"build:stable": "node ../../scripts/build.mjs stable", | ||
"build:node": "node ../../scripts/build.mjs node --ignoreTopLevel", | ||
"build:stable": "node ../../scripts/build.mjs stable --ignoreTopLevel", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not default to using the same bundling approach as in @mui/material? I thought @mui/icons-material was the exception we had, an approach that performs worth in terms of bundle compatibility but leads to a smaller package size.
"build:node": "node ../../scripts/build.mjs node",
"build:stable": "node ../../scripts/build.mjs stable",
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, looking at it again I think I misunderstood. Will create another PR to fix it.
Great to see this change done 👍 |
Related to #35840. All exports must be modules to be able to have nested imports. Similar to #37586