[Fedor Losev]

It seems that WebClipse doesn’t use the compiler configuration of the project properly, not sure is it version related or flags related.

I have a typescript 2.3.2 project and it builds just fine with ng build, etc.

But in IDE project properties / TypesSript I see Detected TypeScript version: 2.2.2 and I see errors in Problems that should appear only below 2.3 or if downlevelIteration is not properly picked from tsconfig.

package.json:

"@angular/cli": "1.0.1"
 "@angular/xx": "^4.1.0"
 "typescript": "^2.3.2"

tsconfig:
"downlevelIteration": true,

some 2.3 code:

const map = new Map<string, string>();
const spread =  [...map.keys()];

ng build / ng lint / ng serve: everything is fine

In WebClipse editor and Problems view there is an error: Type ‘IterableIterator<string>’ is not an array type (same error as if using with ng build with an older typescript version or without downlevelIteration flag in tsconfig).

Does WebClipse incorrectly pick 2.2.2 from angular cli dependencies instead of my package.json?

+>npm list typescript
+-- @angular/cli@1.0.1
| -- typescript@2.2.2
-- typescript@2.3.2

This may be related to this issue, but here I can’t see a tolerable workaround (apart from switching to es2015 target which is not working in IE11 etc.).

[support-swapna]

Fedor,

Sorry that you are seeing this issue. The dev team is looking into it. They will get back to you soon.
Apologies for inconvenience caused.

–Swapna
MyEclipse Support

[support-swapna]

Fedor,

TypeScript 2.3.x is not yet supported in Webclipse. It might take couple of weeks for us to support TypeScript 2.3.x in our tooling. We will keep you posted about the schedule.

Apologies for inconvenience caused.

–Swapna
MyEclipse Support

[Fedor Losev]

I thought WebClipse uses what is configured for the project and cli / ts language services.

So will we always depend on Genuitec to release supporting WebClipse version with lag of few weeks from TypeScript release? They release 1-2 versions every month…

[support-piotr]

Fedor,

Webclipse is using embedded TypeScript version for each minor version, that is 2.0, 2.1, 2.2, etc. We have to ensure that our integrations work with that particular version and from our experience there are always some troubles between angular language-services and each typescript version, or breaks in internal APIs. We are also writing our own extensions for TypeScript like file name refactoring, which have to be tested. We did release TS 2.2 support without extended testing and there were serious breaks, which lead to regressions across the IDE. For instance incremental build was broken due to internal API changes in TS, not mentioning various problems with Angular support. I think you wouldn’t like to have TS 2.3 support if it would for example destroy your source files on refactoring.

I understand your concern and I will ensure that we will do much better with supporting TS 2.4 much sooner than previous releases. Support for TS 2.3 is coming in 3-4 weeks with the next release – CI 6. Due to very overloaded schedule we haven’t been able to include it in the latest one. If there is TS 2.4 GA a week before our next release, I will do my best get support for it into CI6 as well. Thank you for your understanding!

[Fedor Losev]

Yep, I see the complexity and the need to bind explicitly some features and API for each new version.

Obviously, TS evolution pace is something unusual for (almost) mainstream language and I understand it requires some time to figure out the right framework to adapt quickly for these changes. I also think TS will eventually settle with slower rate of breaking changes.

Hope WebClipse will be able manage this complexity and keep the lag small.

[Author]

Posts