-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Bug] - Styled components - Module not found: A package is trying to access a peer dependency that should be provided by its direct ancestor but isn't #966
Comments
|
i fixed the peer dependecies , the same error
when i start the application.I get the following error.
|
You need to set it as a dependency ( |
Ok this was working. To fix this for others "react-is" should be added as peerDependecies in styled-components ? |
It already is, you were missing it as a dependency. |
@merceyz I do not understand it, why should Can you please elaborate your point? |
https://yarnpkg.com/configuration/manifest/#peerDependencies |
styled-components/styled-components#3082 (comment) |
Hello! I tried to fix it with adding this to my .yarnrc.yml but it did not help |
@sibstark Have you ran yarn after adding these lines? |
which command? yarn install? |
Any updates on this issue? Locally everything works, but when I run the same code at Gitlab CI, an error appears. My error log looks like this:
.yarnrc.yml:
|
No, the solution to this issue was specified in #966 (comment). Based on the error and looking at the package in question, the issue in your case is that packageExtensions:
'react-spring@*':
peerDependencies:
'react': '*'
'react-dom': '*' However the provided Since this issue was resolved over two years ago I'll lock this. |
Bug description
It is an CRA with only styled-components as dependencies see below for repo.
What is the current behavior?
Failed to compile.
What is the expected behavior?
dont "crash"
Steps to Reproduce
sorry i dont know how i would do this with sherlock
Environment
2.0.0-rc.29
The text was updated successfully, but these errors were encountered: