-
Notifications
You must be signed in to change notification settings - Fork 50
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
Error when targeting ES2015+ #253
Comments
@tomc974 this should work. Could you provide a bit more information about what you're including in your app and what the run-time error is that you get and in which run-time environments? My guess without having any details is that there may be a missing polyfill or shim that might still be needed for certain features in some browsers. Though it's always possible we missed something, so if you can share more details that would be helpful. Thanks! |
@dylans Thanks for your answer. Here are some details about my environment:
I build the website with
To reproduce, just create a project with |
This appears to be caused in this case by the We do currently ship es2015 classes that are used with the cli-build-widget commands to target evergreen browsers, but do not currently enable that functionality for cli-build-app commands. We would like to switch this up and support evergreen browsers first, as discussed in dojo/cli-build-app#64 and dojo/cli-build-app#65. |
This is fixed as a forwards compatible change by dojo/cli-build-app#100. And will be in cli-build-app version |
Hi,
I'm currently trying to build a simple app with Dojo 2 and used the
dojo-cli
to create a project. I noticed in the generatedtsconfig.json
that the target is set toes5
. With this setting my application is working fine, however if I try to set the target to ES2015+, I get a run-time error.To reproduce this issue, just create a project with
dojo-cli
and change the target intsconfig.json
toes2015
.So now I'm wondering why a brand new framework like Dojo 2 can't be compiled to ES2015+...
The text was updated successfully, but these errors were encountered: