Skip to content
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.

When uglify-js fails to parse, it should throw a more specific Error #835

Open
michaelfranzl opened this issue Nov 25, 2017 · 1 comment

Comments

@michaelfranzl
Copy link

throw new Error(e);

When uglify-js fails to parse (i.e. when some ES6 module was accidently not configured to be transpiled to ES5), it should not simply re-throw the uglify-js error, since it only contains filename: '0'. The error should contain the currently processed fileName. Ideally, the offending line should be output too.

@guybedford
Copy link
Member

Thanks for posting, and apologies for the delay.

I'd be happy to review a PR for this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants