Closed azhiv closed 10 months ago
Hello – sorry I am just now getting to this! You can always set your own options in the tsconfig.json
for things like target
and it will work just fine. We also recommend folks switch to using the combination of ember-cli-babel
as documented here for building apps or a “v2 addon” using Rollup for building addons, using either tsc
or glint
directly and using the @tsconfig/ember
TS config and blueprints generated from Ember itself. (We'll also be updating the docs to suggest that in the next day or two!)
I'm going to close this, but feel free to respond here if you have further questions, and sorry again about the delay.
Please paste the output of
ember -v
herePlease paste the output of
tsc -v
herePlease paste the version of
ember-cli-typescript
andember-cli-typescript-blueprints
herePlease paste your
tsconfig.json
andtslint.json
oreslint.json
(if applicable) belowMy tsconfig.json
My eslint.json
What are instructions we can follow to reproduce the issue?
Reproduction Case
If you can, please try to fork this codesandbox, and give us an example that demonstrates the problem. Paste the link below so that we can see what's going on
Link: https://codesandbox.io/p/sandbox/my-app-forked-uj6vjr?welcome=true&file=%2FREADME.md Your sandbox is a bit outdated so I couldn't get it up and running (it emits a lot of side errors that I couldn't get rid of), but the root problem there is still reproducible.
Another link to the project on github.
Create a new route with the following content:
Now about that bug. What did you expect to see?
I expect the command
ember s
to succeed without errors.What happened instead?
Instead, the build fails with this error:
This is caused by ES5 being utilized as the source of TS type definitions. A similar function call on a very light TS setup succeeds when explicitly configuring ES to smth like 2022. Is there a way to configure ember-cli-typescript to target custom ECMAScript version?