-
Notifications
You must be signed in to change notification settings - Fork 2k
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
React DnD does not provide a default export #408
Comments
Please set a breakpoint during the warning and check the stack trace. File an issue with the relevant project that tries to access the default export (which does not exist). |
It may be for the best but this is a bit annoying and this message is deceiving... |
What is deceiving about it? Have you checked why this other library you are using triggers it? It should be fixable on their side. |
|
Problem could be also context injection into child component or something related to serverside render.
The point is the message does not have anything to do with all this.. |
I don't know why, but it looks like |
I didn’t even know webworkify-webpack exists :-). Apparently here is the access: https://github.com/borisirota/webworkify-webpack/blob/2b7a1e9e82b889aaa17e4d5e40e034bd51b140fa/index.js#L23. I don’t mind removing the warning if it causes much trouble. I’d accept a PR removing it. |
I have also made pull request on webworkify-webpack to check for undefined. |
Fixed in 2.1.3, thanks for the PR! |
Thank you for your help! |
This seams it can trigger error in completely unrelated third party module like for example "mapbox-gl" in my case.
https://github.com/gaearon/react-dnd/blob/master/src/index.js#L7
Error happens when instantiating map otherwise everything works fine. The whole drag and drop also works fine in another page. And if I disable drag and drop then map works ok also.
Error happens when dnd context is set and instantiating unrelated code like map in my case:
Did anyone came across something similar? Anyone has a suggestion to a quick fix, workaround?
Cheers
The text was updated successfully, but these errors were encountered: