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.
UglifyJs Unexpected Token >
See original GitHub issueAfter importing vue-chat-scroll, uglifyjs fails in webpack with the following error:
ERROR in js/vendor.3b917c2.js from UglifyJs
SyntaxError: Unexpected token: operator (>) [js/vendor.3b917c2.js:202508,27]
It still runs properly, but it’s not able to process it, resulting in huge file sizes.
Issue Analytics
- State:
- Created 7 years ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
How I Fixed: UglifyJs Unexpected token: name (DropIn)
As the error states, the issue is with the UglifyJs plugin, which I use in combination with WebPack. This is a frustrating show-stopping...
Read more >UglifyJs unexpected token error - Stack Overflow
Now when i build my webpack with -p, i get the mentioned error, because uglify comes up there. Now, how can i solve...
Read more >webpack uglifyjs plugin fails with "Unexpected token name" for ...
While upgrading our dependencies/build to new @Turf version 5.0.4, I couldn't get passed error below.
Read more >"[webpack] 'dist': web-part.js from UglifyJs Unexpected token ...
js from UglifyJs Unexpected token: name". The reason was the web part was using ES6 code for managing the array objects and UglifyJs...
Read more >JavaScript : UglifyJS throws unexpected token: keyword (const ...
JavaScript : UglifyJS throws unexpected token : keyword (const) with node_modules [ Gift : Animated Search Engine : https://bit.ly/AnimSearch ] ...
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
Yeah I saw that about UglifyJS but it seems the “solution” most people accept is transpiling first. I’m not very frontend-savvy but it seems like a major pain in the butt.
Thanks again for the workaround!
Yes, sorry
1.0.4