Fails in production mode
See original GitHub issueIn development environment my dnd component works excellent. But in production it doesn’t. Multiple Uncaught Error: Expected sourceIds to be an array.
message in console on drag begin. How is it possible?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
Build fails in production mode - Material Design for Bootstrap
Expected behavior When I run ng build --prod to compile my project I expect it to successfully build. Actual behavior I get an...
Read more >An error happens in webpack production mode, but but works ...
An Uncaught TypeError occurred when I use webpack's production mode, but it works well in webpack's development mode.
Read more >Magento 2: Showing error on production mode
I'm facing an issue like errors are show on PRODUCTION mode, how can this be possible. Anyone have ...
Read more >Error when enabling production mode - Magento Forums
Solved: I can't enable development mode after i've installed an extension, the errore that i have is in the screenshot.
Read more >Uncaught error in production mode · Issue #4302 - GitHub
When using redux-form 8.0.4 with react-redux 6.0 there is a bug in production mode (minified code), with throw new Submission Error, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Found out a decent solution. Props to @tambeta for the initial code here
If we take his implementation as is, itll destroy performance if the user hovers the DropTarget since the DropTarget will consistently be forced to rerender. Given our situation, we only want to know if the targets have changed, so we can update his solution to:
then use it:
and it should technically only force a rerender if the targets change.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.