Installation bug Cannot find peer dependency @mui/zero-runtime

[Aya-Alabrash]

Steps to reproduce

Link to live example: (required)

Steps:

1. I followed the installation guide and run npm install @mui/material @emotion/react @emotion/styled
2. Then, I got this error

Current behavior

Expected behavior

Successful installation of @mui/material

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: installation bug

[magnusriga]

I think the problem is here:

material-ui/pnpm-lock.yaml

Line 1538 in 90f655a

'@mui/zero-runtime':

zero-downtime is listed as a direct dependency of @mui/material in the monorepo's lockfile. The lockfile needs to be updated by someone with privileges to run pnpm install and push new lockfile to repo.

The update was done by @brijeshb42 13 hours ago.

[elyobo]

Interim workaround is to go a patch release down - npm i @mui/material@5.15.7

[oliviertassinari]

I changed the latest tag to point to the previous version, Material UI v5.15.8 is corrupted.

npm dist-tag add @mui/material@5.15.7 latest

https://www.npmjs.com/package/@mui/material?activeTab=versions

Root problem seems to #40854 (comment)

[tnguyen14]

@oliviertassinari do you know how esm.sh resolves major semver?

If I go to https://esm.sh/@mui/material, it resolves correctly to https://esm.sh/@mui/material@5.15.7, but if I go to https://esm.sh/@mui/material@5, it resolves to https://esm.sh/@mui/material@5.15.8

[lorand-horvath]

@oliviertassinari If one installs @mui/material@5.15.7, it will still install the newer 5.15.8 dependencies ... which is a bit of a mess.

        "@mui/core-downloads-tracker": "^5.15.7",
        "@mui/system": "^5.15.7",
        "@mui/utils": "^5.15.7",

Is there a workaround until this gets properly fixed?

[oliviertassinari]

I'm reopening per #40971 (comment), problem isn't solved yet. Since this breaks new installations, issues should be closed once released.

For regular issues, its fine to close even before release.

[brijeshb42]

Published v5.15.9 with the fix.

[oliviertassinari]

@brijeshb42 Awesome, thanks for the fix 👍