Better Support for ESNext

[EisenbergEffect]

At present, using ESNext features such as decorators, async/await, class instance fields, etc. results in the editor drawing red squiggles. In the very least, it would be nice if there was an easy way to stop VSCode from complaining about these features in a normal .js file.

Perhaps some thought needs to go into how VSCode will handle the evolution of ES in general. With developers using tools like Babel, and opting into stage-n features before they are finalized as a norm, I think this is going to crop up more and more. Not to mention that popular frameworks like Aurelia, React, Ember and Angular 2 are using these features more.

As for me, I have a hard time recommending VSCode to anyone that isn't doing TypeScript or sticking strictly to ES2015. It gets ugly pretty quick otherwise. I'm looking forward to seeing this improve. It's the only thing really holding me back. Thanks for all the great work so far!

[egamma]

@EisenbergEffect thanks for the feedback.

At present, using ESNext features such as decorators

Actually decorators are supported and you can enable them in the jsconfig.json pls see microsoft/TypeScript#6872 (comment)

async/await, class instance fields, etc. results in the editor drawing red squiggles.

We will add support for disabling the built-in diagnostics, pls see the discussion in #3804 and I'm closing this issue in favor of this one.

[egamma]

closing as a duplicate of #3804

[EisenbergEffect]

@egamma Nice to see you here :)
Thanks for looking into these features. Regarding decorators, it's actually broken on my VSCode instance with the latest release.

[egamma]

@EisenbergEffect this works for me. Tested in 0.10.11:

Error without the experimentalDecorators property:

No error when experimentalDecorators is true:

[EisenbergEffect]

Check this out:

One thing that is different from your example above is my folder structure. I have something like this:

[egamma]

I also see that you have both a jsconfig.json and a tsconfig.json. Is it a mixed .js and .ts project? If yes then you can set allowJS to true in the tsconfig.json and then you can delete the jsconfig.json. If it is a .js project only then I would delete the tsconfig.json.

[EisenbergEffect]

If I remove the tsconfig, the problem goes away :)

It's not a mixed project per se. I was working on a sample app for an Aurelia workshop I'm going to be running. I included the tsconfig because I suspect some students will want to use TS instead of Babel. So, it was there out of a convenience for them. However, I should probably provide them with a complete TS setup separate from this one. Having both clearly causes the issue and probably doesn't make sense.

Thanks!

[egamma]

👍 on separate .ts and .js setup.