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.

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

@material-ui/styles duplication issue #15

Closed
potier97 opened this issue May 2, 2020 · 4 comments
Closed

@material-ui/styles duplication issue #15

potier97 opened this issue May 2, 2020 · 4 comments

Comments

@potier97
Copy link

potier97 commented May 2, 2020

yarn list @material-ui/styles when i was add material-ui/core, and rsult in :

├─ @material-ui/styles@4.9.6
├─ @react-material-ui-carrusel
│ └─ @material-ui/styles@4.9.10

@Learus
Copy link
Owner

Learus commented May 2, 2020

Hello.
Since I do not exactly know why and how this is a problem, could you please elaborate?
From my understanding, material-ui/styles is a dependency of the carousel component.
How would that be a problem, and how could I solve it?

@potier97
Copy link
Author

potier97 commented May 2, 2020

Hello, that becomes an error at the moment in which the dependency is called the same as the material library or there is a reason that it can break and not apply the classes that are being carried out with this material library, wey. This seems like a Warning in the Google Chrome debugger so it is necessary to change it to avoid future problems with styles, I solved it by deleting the yarn.lock file and reinstalling the dependencies.

@Learus
Copy link
Owner

Learus commented May 7, 2020

Hello, sorry for the late response.

I've looked up the problem, and I have to point out some things.

  • The library does not have @material-ui/styles as a dependency and is not shipped with it. It does have @material-ui/core though, that contains /core/styles. I do not know if this could be a problem.
  • Check following issues. I believe Issue2 is the warning you are talking about?
  • Have you tried duplicate detection tools like npm dedupe?

Does this problem get resolved by deleting your lock file and fixing deps on your side, or is there something I should do on my side?

@Learus
Copy link
Owner

Learus commented Jun 3, 2020

Since there hasn't been any activity regarding this issue, I am closing it for now.

@Learus Learus closed this as completed Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants