-
Notifications
You must be signed in to change notification settings - Fork 94
Receiving a react error that prop-types could not be found #115
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
Comments
Hey Josh, thanks for reporting! The whole idea behind this is that Could you maybe provide an example to demonstrate the issue? I have no experience with pnpm myself. |
Closing due to inactivity, and because the obvious workaround is to just install |
@ghengeveld Can we reopen this? I'm seeing the same issue. 🙂 As with @sadsa, we're using Yarn's PnP ("Plug and Play") feature. This feature makes it so when a library tries to load a dependency that's not specified in its package.json file, an error is thrown. This error is thrown while compiling via webpack. The error:
Would it be possible to specify Thanks 🙂 |
Hi @ghengeveld, Just following up on this. Can we please reopen this bug? 🙂 |
When using the PNPM package manager, any dependecies not explicitly mentioned in the
package.json
will be ignored at time of package installation.The following code (found in
dist-web/index.js
) make the following reference to theprop-types
package.React apps throw an error, complaining that the
prop-types
package could not be resolved.The fix, is to add
prop-types
as a dependency in thepackage.json
.I will commit a PR to hopefully which fixes the issue.
The text was updated successfully, but these errors were encountered: