-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Cannot find module './factoryWithThrowingShims' #134
Comments
Can you make a repo that reproduces the issue? Tried clearing npm cache? |
Just added react-responsive to my project and can confirm the issue. Also am using browserify (via browserify-rails) and babel (with 'es2015' and 'react' presets). |
Pushing up a maybe-fix as 4.0.1, give it a try and let me know if it works. Clear npm and cache then reinstall it. Something to do with prop-types being bundled which would cause an issue on browserify, not 100% sure. |
@contra Thanks. I wasn't able to try out your change because it doesn't seem to be available on npm, but I did make a simple repo that reproduces the error - https://github.com/collinksmith/react-responsive-test. |
@collinksmith Publish didn't finish - should be good now. 4.0.2 |
Still getting the error in 4.0.2. There is no version 16.0.0 of |
Ah, I found the issue. webpack only transforms code blocks that are accessed, there is a I would say both webpack and browserify are being stupid here. Anyways, I'll add something to minify out the dead code so browserify doesn't blow up on it. |
@collinksmith Published as 4.0.3 |
Fix confirmed, thanks! |
Same error as #123, but clearing node_modules and installing from scratch did not resolve it.
My build process uses gulp and browserify. I get the same error for both prod and dev builds.
The first version in which I get this error is v2.0.0, and it is still present in v4.0.0. It looks like the line that throws the error was added in the commit to update webpack, and the missing file seems to be from prop-types.
Full error message:
The text was updated successfully, but these errors were encountered: