[internal] Update browser support versions

[siriwatknp]

See #40958

• I started to work on this because of [material-ui][Button] Convert to support CSS extraction #41378
• Run npx browserslist --mobile-to-desktop "> 0.2%, last 2 versions, Firefox ESR, not dead"
• Remove legacy since we no longer support IE move to the next PR
• Update node version from npx browserslist "maintained node versions"

---

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

Netlify deploy preview

• docs/data/material/getting-started/supported-platforms/supported-platforms.md

@material-ui/core: parsed: -1.08% 😍, gzip: -1.35% 😍
@material-ui/lab: parsed: -0.90% 😍, gzip: -1.14% 😍
@material-ui/system: parsed: -0.90% 😍, gzip: -0.90% 😍
@material-ui/unstyled: parsed: -2.88% 😍, gzip: -2.47% 😍
@mui/joy: parsed: -2.60% 😍, gzip: -2.98% 😍

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against c73c022

[Janpot]

There is also a "legacy" env in the babel config

material-ui/babel.config.js

Line 16 in f6a89c1

const useESModules = api.env(['regressions', 'legacy', 'modern', 'stable', 'rollup']);

[siriwatknp]

Checking it again, I found several places related to IE11 to remove and I am afraid that this PR might be too big to review, so I will bring the legacy back and split the PR.

[michaldudak]

It does work in Base UI: https://github.com/mui/base-ui/blob/master/.browserslistrc
Have you tried updating caniuse-lite to the latest version?

[siriwatknp]

Let me try

[siriwatknp]

@michaldudak It really because of caniuse-lite. However, I don't see any usage of "caniuse-lite" in any of the package.json, so I make it work with pnpm up "caniuse-lite". Is it the correct way to upgrade implicit deps? cc @Janpot

[Janpot]

Is it the correct way to upgrade implicit deps?

👍 Probably also want to run pnpm dedupe after. But I see no problem with this.

[Janpot]

@siriwatknp Actually, it seems to be

npx browserslist@latest --update-db

[DiegoAndai]

We agreed upon Safari 15.4 for v6 at #40958 (comment)

[siriwatknp]

Thanks for pointing that out. Will update it. cc @michaldudak Would you like to use the same list for Base UI?

[michaldudak]

We'll decide when it's closer to our release. Thanks for letting me know.

[Janpot]

@siriwatknp Regarding node.js upgrade, have you seen the debates in mui/mui-x#10997 and #32546?

[siriwatknp]

@siriwatknp Regarding node.js upgrade, have you seen the debates in mui/mui-x#10997 and #32546?

Thanks, I will remove nodejs update from this PR.

[Janpot]

Looks good. Last suggestion: If it makes sense, add a package.json script for updating the browserslist. And an instruction in the .browserslistrc file to run the script on major versions?

"update-browserslist": "browserslist@latest --update-db && browserslist@latest --mobile-to-desktop \"> 0.2%, last 2 versions, Firefox ESR, not dead\""

[LukasTy]

Looks good. Last suggestion: If it makes sense, add a package.json script for updating the browserslist. And an instruction in the .browserslistrc file to run the script on major versions?

@Janpot I'm not sure if this is better. 🤔
There is no easy way to leave comments in package.json and in this case, we have a custom decision for Safari support.
IMHO, the current solution is a bit more flexible.
Adding it to the major release instruction guide makes sense in any case, we can refer to the browserlisrc file and link a reference PR/issue. 👌

[Janpot]

Fair enough. Some release instructions makes sense as well. Maybe it makes sense to mention the browserslist@latest --update-db command?

[LukasTy]

Fair enough. Some release instructions makes sense as well. Maybe it makes sense to mention the browserslist@latest --update-db command?

Oh yes, that makes sense. I've done it manually by removing the lock entry and rerunning the install. 🙈 😆
BTW, your example probably misses the npx at the start, because we do not list browserslist as a direct dependency. 🤔

[DiegoAndai]

Small fix on the documentation. Otherwise LGTM 👍🏼

[siriwatknp]

Fair enough. Some release instructions makes sense as well. Maybe it makes sense to mention the browserslist@latest --update-db command?

Added a note to run npx update-browserslist-db@latest after updating the browser versions. browserslist@latest --update-db is deprecated.