[pickers] unmet peer dependency issue

[JinuYong]

Steps to reproduce

Link to live example: (required)

Steps:

1. install mui/x-date-pickers etc,
2. delete node_modules folder
3. yarn install

Current behavior

Hi, I was using the same version of mui and x-date-pickers as shown in the image below.
and I have installed all the packages required for x-date-pickers.

�However not only me, but also my team members are getting the warning as shown in the image below when installing the packages.

Expected behavior

Should install without warning

Context

We used yarn as our package manager.

Your environment

npx @mui/envinfo

  System:
    OS: macOS 14.6.1
  Binaries:
    Node: 20.14.0 - /usr/local/bin/node
    npm: 10.7.0 - /usr/local/bin/npm
    pnpm: 9.12.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 130.0.6723.92
    Edge: Not Found
    Safari: 17.6
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3 
    @emotion/styled: ^11.13.0 => 11.13.0 
    @mui/core-downloads-tracker:  6.1.1 
    @mui/icons-material: ^6.1.1 => 6.1.1 
    @mui/material: ^6.1.1 => 6.1.1 
    @mui/private-theming:  6.1.1 
    @mui/styled-engine:  6.1.1 
    @mui/system:  6.1.1 
    @mui/types:  7.2.17 
    @mui/utils:  6.1.1 
    @mui/x-date-pickers: ^7.20.0 => 7.20.0 
    @mui/x-internals:  7.20.0 
    @types/react: ^18.3.3 => 18.3.8 
    react: ^18.3.1 => 18.3.1 
    react-dom: ^18.3.1 => 18.3.1 
    typescript: ^5.5.3 => 5.6.2 

Search keywords: peerDependency mui/system x-date-picker

Search keywords:

[JinuYong]

Sorry, I registered the issue with the wrong account, so I closed it and reopened it.

[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

@JinuYong 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.

[LukasTy]

@JinuYong Could I ask for the reason for reopening this issue? 🤔