-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Optional chaining operator does not compile #15827
Comments
@sbc100 might this also be fixed by the recent terser update? |
Yup! Looks like this works now. Thanks for following up. |
Nope, I spoke to soon. Seems to still be an issue. |
Looks like the version of terser we updated to still doesn't support |
This just bit me as well. I was inspired by this sample code from here:
My code was compiling & running with Debug or RelWithDebInfo builds, but my Release build was failing during the link stage with the same cryptic error:
When I instrumented terser.js file to print out node.type, I found "ChainExpression", and after figuring out what a ChainExpression was, I replaced the So, I'm happy for now and very appreciative of the work put into emscripten, but it took a while to figure out that optimized release builds are allergic to |
I was hoping this version would make optional chaining work but sadly it looks like we will need to update v5 for that to work. See #15827
I was hoping this version would make optional chaining work but sadly it looks like we will need to update v5 for that to work. See #15827
This does not compile:
Error message:
This might be related to other problems with terser: #13297, #12410
Version of emscripten/emsdk:
Failing command line in full:
The text was updated successfully, but these errors were encountered: