[core] True ESM support

[oliviertassinari]

Steps to reproduce

I'm creating this issue as an umbrella to solve ESM support in Material UI v7.

What does success looks like?

• We close those issues

  • [ESM] @mui/icons-material move to pure ESM #35233
  • [ESM] Publish packages in ESM module format #30671
  • [ESM] Feature a distribution compatible with Node in "type": "module" #37335
  • [ESM] Webpack 5 - NodeJs Server #30525
  • [ESM] Vite + vitest + @mui/material v5.11.0 - createPalette.js:1 seems to be an ES Module but shipped in a CommonJS package.  #35773
  • [ESM][core] Add exports to the package.json #26254
  • [core] Hydration error using nextjs turbopack and icons-material #44055
  • Material UI v6 + Remix + Vite running with “Prop className did not match” error #43980
  • [icons-material] Importing from @mui/icons-material throws error in Remix/Vite #44265
  • Uncaught TypeError: SvgIcon_default is undefined with vite in dev mode after @mui/[email protected]+ #44180
  • MUI not working with React Router 7 and Vite #45018
  • MUI React Component Library / Fails in all modes dai-shi/waku#428
  • Popper.js:11 Uncaught TypeError: styled_default is not a function at Popper.js:11:20  vitejs/vite#12423

• Likely same root cause

  • TypeError: createTheme_default is not a function #43433
  • Box modules is broken #43242

• https://github.com/wooorm/npm-esm-vs-cjs/blob/c0a92334da4979f7614143734bbe7931d2a0dcde/data/2024-08-28.json#L2626 is no longer flagged as "faux" but "dual", see their legend description.

Current behavior

No response

Expected behavior

No response

Context

No response

Your environment

npx @mui/envinfo

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: -

[DiegoAndai]

One of the proposals in #35233 was changing the icons package to be ESM only. This would help reduce the size of the package to 2/3 of its current size (keep type definitions and ESM, remove CJS). Should we do that for v7? @Janpot

[Janpot]

for v7 I'd like to go to dual mode packages with exports field and a single layout that's the same across all packages. Personally I think if we go ESM only with one package we should do it for all. The less we confuse bundlers, the better 🙂

[DiegoAndai]

That makes sense 👍🏼