-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
Fix moduleResolution:node for icons #45444
Conversation
Netlify deploy previewhttps://deploy-preview-45444--material-ui.netlify.app/ Bundle size report |
@@ -37,7 +37,8 @@ | |||
"release": "pnpm build && pnpm publish", | |||
"test": "cd ../../ && cross-env NODE_ENV=test mocha 'packages/mui-material/**/*.test.?(c|m)[jt]s?(x)'", | |||
"typescript": "tsc -p tsconfig.json", | |||
"typescript:module-augmentation": "node scripts/testModuleAugmentation.js" | |||
"typescript:module-augmentation": "node scripts/testModuleAugmentation.js", | |||
"attw": "attw --pack ./build --exclude-entrypoints esm modern --include-entrypoints Button styles" |
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.
Should we add the attw
check for all packages?
Why exclude esm and modern?
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.
I added a few key packages that most people would use, and the icons that have a more exotic setup. didn't want to add too much to CI for packages that most people won't import and that won't regress on their own anyway as it all uses the same automation. We can remove the exclusions after arethetypeswrong/arethetypeswrong.github.io#242 is fixed.
Fix "moduleResolution: node" for the icons package as per #43938 (comment)
We moved to a single declaration file for all icons but this breaks under classic module resolution. This can be fixed using
typesVersions
.I'm also adding
attw
checks in CI to avoid this from regression again. (Opening arethetypeswrong/arethetypeswrong.github.io#242 along the way)