Error in production enviroment
See original GitHub issueI use Sortable-tree in my project, works fine in development enviroment, but after running npm run build
I get the following error in the browser console:
main.js:910 Uncaught TypeError: n is not a function at Object.<anonymous> (main.js:910) at t (main.js:28) at Object.<anonymous> (main.js:1062) at t (main.js:28) at Object.<anonymous> (main.js:1029) at t (main.js:28) at main.js:82 at main.js:82 at main.js:2441 at Object../node_modules/react-sortable-tree/dist/main.js (main.js:2441)
this only happen in production enviroment.
How can i fix that?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
5 Tips To Quickly Tackle Errors in Your Production Code
We will take a look at some simple solutions that can be used to find errors in production as well as ways to...
Read more >DebuggerEvents error in Production Environment - OutSystems
Hello. I got the following error in service center, in Production environment: The file '/<ModuleName>/_debuggerEvents.ashx' does not exist.
Read more >How should you handle errors in a production environment?
There's no single good approach to handling errors, since how an error should be handled completely depends on the exact situation.
Read more >Error coming in Prod - Studio - UiPath Community Forum
Hi All, From yesterday i got error in one of my process in Production. here i am attaching the screenshot of that, can...
Read more >12 Feelings Every Developer Has After Introducing an Error to ...
Waiting for your code to compile? Trying to find the root cause of an issue you've encountered? Here are a few Gifs that...
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
Any update to this? I’m experiencing the same issue:
Webpack config:
webpack.config.prod.js
I fixed my issue by disabling code split.