[data grid] All locales are present in production bundle when using pro/premium

[ddolcimascolo]

Steps to reproduce

Steps:

1. Open this link to live example: https://github.com/ddolcimascolo/mui-x-datagrid-premium-locales
2. Run npm i followed by npm run analyze and examine the bundle analysis

Current behavior

All locales are in the final bundle

Expected behavior

Only the imported locales are in the production bundle.

Context

I'm trying to reduce my bundle size.
Note that importing from @mui/x-data-grid (the free version) works as expected, but I don't think I have to install it when I'm using the premium one...

Your environment

npx @mui/envinfo

System:
    OS: Linux 6.8 Linux Mint 22.1 (Xia)
  Binaries:
    Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v22.11.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 132.0.6834.83

Search keywords: datagrid premium locales

Order ID: 78178

[ddolcimascolo]

Please also note that the problem is not there with pickers locales, even imported from @mui/x-date-pickers-pro

David

[michelengelen]

That is indeed strange... the structure is the same for pickers-pro and data-grid-pro/-premium. We use export * from '<base-package>/locales for both.

@arminmeh do you know why it behaves like this?

[arminmeh]

We are just re-exporting locales from the community package.
Compiled, this does not allow proper tree shaking. Same happens with the Pro package.

I will put this on the board.

@ddolcimascolo, as a temporary workaround, you can import locales from @mui/x-data-grid. This does not require any additional dependency, since @mui/x-data-grid-premium depends on @mui/x-data-grid and you should have it in your node_modules already.

[ddolcimascolo]

We are just re-exporting locales from the community package. Compiled, this does not allow proper tree shaking. Same happens with the Pro package.

I will put this on the board.

@ddolcimascolo, as a temporary workaround, you can import locales from @mui/x-data-grid. This does not require any additional dependency, since @mui/x-data-grid-premium depends on @mui/x-data-grid and you should have it in your node_modules already.

Thx for confirming this as a bug. I was aware of the workaround and can confirm it works.

David