You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that this has come up before and it was dealt with in a PR. However there is still and issue. Webpack has a bug (that I'm trying to get tracked down) where the resolution graph gets messed up and results in prop-types trying to require itself.
This typically is due to web pack's resolve.modules being incorrectly used with a non-absolute path – see rebassjs/grid#51 (comment)
Regardless of what I rename the local module file in this library, the issue could come up with any npm package that shares the same name. Short of namespacing modules in this package, which should be unnecessary due to how modules work by default, there's not really a great way to avoid this sort of thing, and you should ensure that your application's module aliasing doesn't cause it to behave in non-standard ways.
Hope that helps and let me know if that doesn't resolve the issue.
I understand that this has come up before and it was dealt with in a PR. However there is still and issue. Webpack has a bug (that I'm trying to get tracked down) where the resolution graph gets messed up and results in
prop-types
trying to require itself.Here's a gist of what I'm seeing: https://gist.github.com/zentuit/af24021fa3d95b340413587c4984432e
React's
prop-types
is moduleId 48 and styled-system'sprop-types
is moduleId 528. Instead ofI'm getting
The text was updated successfully, but these errors were encountered: