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.
Unexpected character '@' (from UglifyJs)
See original GitHub issueLook like it’s time to deprecate UglifyJs and move to https://github.com/terser-js/terser
It’s easy to reproduce the problem - just ignore @babel/runtime in .size-limit
[
{
path: "dist/es2015/index.js",
limit: "5 KB",
ignore: ["prop-types","@babel/runtime"]
}
]
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Unexpected character ( ` ) error when using UglifyJS?
I read that I would need to transpile it down to ES5, but I'm new to this and I'm not sure how to...
Read more >Issue #2060 · mishoo/UglifyJS - Unexpected character - GitHub
Uglify version (`uglifyjs -2.4.0) I get this error during compile time on ... UglifyJs SyntaxError: Unexpected character '`' [application-a8708.
Read more >Help uglify-js - Unexpected character '`' Azure pipeline - Reddit
https://stackoverflow.com/questions/68636023/uglify-js-syntaxerror-unexpected-character-azure-pipeline.
Read more >Uglification Failed. Unexpected Character ' - ADocLib
it complains at the character:.The character is valid for the apple's JS framework.I can't see anything inside the uglify package to ignore those...
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
Open new issue with full details on the error
Webpack moved to Tenser. Seems like issue was fixed.