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

Fix moduleResolution:node for icons #45444

Merged
merged 4 commits into from
Mar 3, 2025
Merged

Conversation

Janpot
Copy link
Member

@Janpot Janpot commented Feb 28, 2025

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)

@Janpot Janpot added regression A bug, but worse scope: code-infra Specific to the core-infra product labels Feb 28, 2025
@Janpot Janpot mentioned this pull request Feb 28, 2025
31 tasks
@mui-bot
Copy link

mui-bot commented Mar 1, 2025

Netlify deploy preview

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

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 3fd4d69

@Janpot Janpot marked this pull request as ready for review March 1, 2025 15:33
@Janpot Janpot requested a review from DiegoAndai March 1, 2025 16:12
@@ -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"
Copy link
Member

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?

Copy link
Member Author

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.

@Janpot Janpot merged commit 793ca53 into mui:master Mar 3, 2025
19 checks passed
mnajdova pushed a commit to mnajdova/material-ui that referenced this pull request Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression A bug, but worse scope: code-infra Specific to the core-infra product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants