Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

@emotion/react multiple instances (versions) when using with pnpm workspaces #35526

Closed
2 tasks done
oalexdoda opened this issue Dec 18, 2022 · 4 comments
Closed
2 tasks done

@emotion/react multiple instances (versions) when using with pnpm workspaces #35526

oalexdoda opened this issue Dec 18, 2022 · 4 comments
Labels
duplicate This issue or pull request already exists support: Stack Overflow Please ask the community on Stack Overflow

Comments

@oalexdoda
Copy link

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Steps to reproduce 🕹

Link to live example:

Steps:

  1. Set up a pnpm workspace with a package (project) using @mui
  2. Run dev
  3. You'll get errors in the console saying there's multiple @emotion/react instances (seems related to how the lock file is generated with multiple versions).

You can try this with the next.js example in the examples folder.

Current behavior 😯

Errors out, prevents the ability to use @mui + emotion in a workspace completely.

Expected behavior 🤔

No errors, just like when using it individually.

Context 🔦

No response

Your environment 🌎

System:
OS: macOS 13.1
Binaries:
Node: 18.12.1 - /usr/local/bin/node
Yarn: Not Found
npm: 8.19.2 - /usr/local/bin/npm
Browsers:
Chrome: Not Found
Edge: Not Found
Firefox: Not Found
Safari: 16.2
@oalexdoda oalexdoda added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Dec 18, 2022
@oalexdoda
Copy link
Author

This causes the server/client to produce different classes, effectively breaking @mui completely. So it's not just a warning.

@zannager zannager added the core Infrastructure work going on behind the scenes label Dec 19, 2022
@mnajdova
Copy link
Member

@altechzilla sounds like a duplicate of #35006

@mnajdova mnajdova added duplicate This issue or pull request already exists support: Stack Overflow Please ask the community on Stack Overflow and removed core Infrastructure work going on behind the scenes status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Dec 19, 2022
@github-actions
Copy link

👋 Thanks for using MUI Core!

We use GitHub issues exclusively as a bug and feature requests tracker, however,
this issue appears to be a support request.

For support, please check out https://mui.com/getting-started/support/. Thanks!

If you have a question on Stack Overflow, you are welcome to link to it here, it might help others.
If your issue is subsequently confirmed as a bug, and the report follows the issue template, it can be reopened.

@ricardosc12
Copy link

no answer for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists support: Stack Overflow Please ask the community on Stack Overflow
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mnajdova @oalexdoda @ricardosc12 @zannager