Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issues with Babel 6 and various parser issues #895

Closed
ghost opened this issue Dec 17, 2015 · 8 comments
Closed

issues with Babel 6 and various parser issues #895

ghost opened this issue Dec 17, 2015 · 8 comments

Comments

@ghost
Copy link

ghost commented Dec 17, 2015

Hey, @pirxpilot @glasser @lautis @devongovett

I use let instead of var in my code. And end up with this issue:
stack: 'Error\n at new JS_Parse_Error (eval at <anonymous>

If I change it so Im using var, everything works just fine. Until it throws this:

JS_Parse_Error { message: 'Unexpected token punc «(», expected punc «:»', filename: 0,

I haven't managed to track down yet what cause this.

Any solutions? I was looking for other options then UglifyJS, but this seems to be the best tool.

I'm using this together with Rollup, and this option activated: fromString: true,

Any ideas what's going on? Or how to solve this?

@avdg
Copy link
Contributor

avdg commented Dec 17, 2015

All I can say now is that UglifyJS doesn't support Ecmascript 6/2015 yet and that the development of this specification is done on the harmony branch which is still under development.

So there are no features on master yet like let, const, destructured assignment,...

@ghost
Copy link
Author

ghost commented Dec 17, 2015

Ah okay. That explains it! Thanks :)

@coreybutler
Copy link

Any update on this? Webkit now has 100% ES2015 support (coming in Safari 10) and all of the major browsers natively support let/const now.

@avdg
Copy link
Contributor

avdg commented Jun 25, 2016

Please use the harmony branch (for let). The branch is still considered unstable and progress can be tracked on #448.

@avdg
Copy link
Contributor

avdg commented Jun 25, 2016

Uh, I would be interested in the bug on master as well. The master branch should normally be stable and bugs do get fixed if they are specified and given attention to.

@avdg
Copy link
Contributor

avdg commented Jun 25, 2016

Errors should normally indicate where it crashed, and mostly the bug should be caused at the position the error is given, or before.

@avdg
Copy link
Contributor

avdg commented Jun 25, 2016

Issue might be #1144, but uglify is strict 5.1 on master and we don't support older version or malformed outdated interpreters.

@alexlamsl
Copy link
Collaborator

Closing as duplicate of #448.

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

No branches or pull requests

3 participants