[question] Does MUI and MUI-X require the minimum version of node library?

[moonerr]

Order ID 💳

#39623

The problem in depth 🔍

Hi, the latest types/react upgrades have affected a lot of developers. Unfortunately, our dev team is no exception, with several type-check errors and broken component properties.
According to the mui website, we have to keep updated to the latest version of types/react. So I wondered if mui or mui-x requires a minimal version of the node library as well. And could you please also give me any suggestions on how we manage the library upgrades?
Thanks.

Your environment 🌎

`npx @mui/envinfo`

    System:
    OS: Windows 10 10.0.19043
  Binaries:
    Node: 14.18.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD  
    npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD  
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.53)
  npmPackages:
    @emotion/react: ^11.5.0 => 11.9.0
    @emotion/styled: ^11.3.0 => 11.8.1
    @mui/base:  5.0.0-alpha.72
    @mui/icons-material: 5.6.2 => 5.6.2
    @mui/lab: 5.0.0-alpha.73 => 5.0.0-alpha.73
    @mui/material: 5.5.3 => 5.5.3
    @mui/private-theming:  5.8.0
    @mui/styled-engine:  5.8.0
    @mui/styles: 5.5.3 => 5.5.3
    @mui/system:  5.8.0
    @mui/types:  7.1.3
    @mui/utils:  5.8.0
    @mui/x-data-grid: 5.7.0 => 5.7.0
    @mui/x-data-grid-pro: 5.7.0 => 5.7.0
    @types/react: 16.9.20 => 16.9.20
    react: ^17.0.0 => 17.0.2
    react-dom: ^17.0.0 => 17.0.2
    typescript: ^4.5.2 => 4.6.4

[cherniavskii]

According to the mui website, we have to keep updated to the latest version of types/react

Are you referring to v4 to v5 migration guide? MUI packages do not require the latest version of @types/react, for example @mui/material supports both v17 and v18 of @types/react (see https://unpkg.com/browse/@mui/[email protected]/package.json)

So I wondered if mui or mui-x requires a minimal version of the node library as well

No, MUI packages do not require node at all, since those are client-side libraries.
But other tools you might use (e.g. CRA, Next.js, Gatsby) do require node. That's out of MUI's scope though.

And could you please also give me any suggestions on how we manage the library upgrades?

Can you elaborate more on the problem you experience? Did you upgrade from v4 to v5? Do you use @mui/material as well?

[cherniavskii]

Just an update on node.js topic - if you use server-side rendering, MUI requires minimum v12.17 of node (or 12.0 with --experimental-modules enabled) - see https://mui.com/material-ui/getting-started/supported-platforms/#server
But for example latest Next.js requires node >=12.22.0, CRA requires node >=14.0.0, so you won't be impacted by MUI node requirement anyway

[oliviertassinari]

It looks like we are good on this one closing. I have created mui/base-ui#1522 to make sure we don't regresse on this in the future.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@moonerr How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.