Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error appears in a production build
See original GitHub issueHi Everything works nice in dev. build, but when building for production (NODE_ENV=production) dnd doesn’t work. I’m able to pick a draghandle but every single px moved produces the following error:
(22) index.js:593 Uncaught ReferenceError: a43326 is not defined
at n.value (index.js:593)
at t.handleSortMove (index.js:272)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:9
Top Results From Across the Web
Nextjs project is showing build error only on production build.
Hello,. our team is currently having some build issues with Vercel, the situation being the whole project builds just fine on preview ...
Read more >node.js - Development build errors showing in production ...
I have a NodeJS app, built with ReactJS, deployed on Heroku which is showing errors that should only be visible ...
Read more >Error in nextjs production build (Just in production)
Hi! We are running our app with builder within a vercel deployment, directly forking nextjs-builder-io-landing-page builderio github ...
Read more >JS errors for a React app showing in development but not in ...
... and I'm able to see the js errors while in development, but as soon as I created a production bundle(yarn run build...
Read more >Typescript errors only when building for production - Laracasts
Hi, I have build a project in Laravel and Vue that has been working for about a year. It is a simple project...
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 Free
Top 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
@ambewas disabled hoist_props and it worked! great! thanks guys!
I’ve opened up an issue with uglifyJS https://github.com/mishoo/UglifyJS2/issues/2540
let’s see what comes out of that. Their latest release 3.2.0 could be the one that breaks things here.