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 with UglifyJS2 and webpack 2
See original GitHub issueI’ve recently upgraded a project from webpack 1 to 2 and I’m encountering an error when trying to minimize output from svg-sprite-loader.
ERROR in app.bundle.js from UglifyJs Unexpected token: operator (>) [app.bundle.js:140332,20]
It works fine as long as i don’t add the UglifyJSplugin. Has anyone run into something similar?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
9 - Stack Overflow
webpack 2 : ERROR in ./public/bundle.js from UglifyJs Unexpected character '`' · shouldn't the behaviors of webpack -p and webpack -d be the...
Read more >Webpack fails in production mode while running uglifyjs ...
BUG What is the current behavior? Execution fails in production mode while using minimiser (aka uglifyjs-webpack-plugin).
Read more >TerserWebpackPlugin | webpack
UglifyJS is a JavaScript parser, minifier, compressor and beautifier toolkit. webpack.config.js module.exports = { optimization: { minimize: ...
Read more >uglifyjs-webpack-plugin - npm
This plugin uses uglify-js to minify your JavaScript. Requirements. This module requires a minimum of Node v6.9.0 and Webpack v4.0.0.
Read more >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 >
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
Nevermind. I found the root of the issue and it was in my own config. Thanks anways!
@psachs21 What was the issue? We’re experiencing the same stuff with our codebase.