-
Notifications
You must be signed in to change notification settings - Fork 958
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 call file using createBrowserHistory history.js #793
Comments
I have same problem 😂 |
Facing the same problem. Is there a fix for this? |
I'm fighting the same issue right now. I suspect that there's some kind of version mismatch going on, but thus far have been unsuccessful in determining the issue. |
|
I'll leave this here since it might help someone else with this issue, although I don't think it was related to this library at all. The issue I was having was my This was likely caused by my webpack configuration, but I figured I'd leave this info here for the next poor soul should someone else run into this issue. If someone knows how/why this problem was actually happening, I'd love to hear it. |
I just ran into the same problem while trying to upgrade to webpack 5. I thought it was my babel or webpack configuration. I found this bug, renamed it to |
Version
History version is 4.9.0
Description
Here is my setup, using webpack with react-router-dom. Trying to create a global file exporting a history object, but it is causing a lot of trouble...
package.json
index.jsx
containers/App.jsx
history.js
webpack.config.js
And here's what webpack build output shows:
When opening the web page I get this error (and the history is clearly not working)
Workaround
But when I rename the history.js file to notHistory.js and rename the import in App.jsx, the history does work and the module exports the history object as expected!
The workaround seems ugly and it indicates that there is probably a mistake in my webpack config, any ideas?
The text was updated successfully, but these errors were encountered: