-
-
Notifications
You must be signed in to change notification settings - Fork 556
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
Error: Cannot find module './factoryWithThrowingShims' from '/app/node_modules/react-redux-firebase/dist' #128
Comments
What version did you npm install? You can check using Also, what did you specify in your Seems like it might be a loader issue since |
getting this with doing a little bit of digging it seems like it might be something to do with PropTypes being abstracted from the react library? Just a thought, haven't dug into the code too much. |
Interesting thought @DavidBrear. Have you tried older versions of react-redux-firebase (i.e. Have you tried a v15 version of My guess is still that it is due to webpack loader parsing. If a reproduction repo can be provided or webpack loader config is provided, it would be easier to know. |
Moving to |
@DavidBrear That would be great. This is one of the last things to get ironed out before the If we can't get it ironed out, we might have to go back to not using |
@DavidBrear This means you should be able to use Note: Issue remaining open until this is out of pre-release |
|
Im still getting this error:
my version react-redux-firebase@1.5.0-alpha |
@miketamis What is your webpack config? Are you using webpack 1 or 2? Can anyone provide a repo where this can be reproduced? |
Another theory: It may have to due with Again, can only be tested/confirmed if a repro is provided. |
i have the same problem using react and react native |
Yeap this error for me was with Expo. I fix it by putting the proptype repo into the react-redux-firebase dist folder in node_modules (obviously not a good fix) |
@ricardokdz and @miketamis ok, going to try some stuff and hopefully get a alpha.2 version out soon that address this |
@miketamis Does not work for me. How's your directory structure? |
@ricardokdz The directory structure shouldn't be causing any issues. I have been using both the material example and the react-native examples to test. Can you provide a repo that you are working on to reproduce the issue? For now I am just having to guess at things that might fix the issue. |
@ricardokdz @miketamis @karltaylor What version of webpack are you using? Can you possibly post your webpack.config? If using webpack 2, how do your webpack configs compare to the webpack2 example? I am able to use browser fieldIt has come to my attention though that more often that not (seems like it is happening in your case) bundling libraries end up using the If we can confirm that this is what is happening, I can release |
### Description Removed `browser` field from `package.json` in attempt to solve #128 ### Check List - [X] All tests passing - [X] Docs updated with any changes or examples ### Relevant Issues * [#128](https://github.com/prescottprue/react-redux-firebase/issues/#128)
@ricardokdz @miketamis and @karltaylor Please let me know if any of you get a chance to try this out or can provide a repository where I can reproduce the issue so the fix can be confirmed. |
|
I have the same error, im using react-dom 16 and no other library |
@stevematdavies This issue is from a while back and should be solved by being up to date. A few questions would help me get to the bottm of it faster:
|
https://webpack.js.org/configuration/externals/ try add prop-types library to external field. |
@imdragonet Do you mean within From what I thought (could be totally wrong), it was supposed to be a dependency handled by any library using it instead of a peer dependency. Open to doing that though if it some are still seeing this issue. |
Can anyone help me on this? error: bundling failed: Error: Unable to resolve module
|
Just did a fresh npm install on a new project and imported into my project and got
The text was updated successfully, but these errors were encountered: