Angular-cli: typescript 2.4 support

[xnnkmd]

Bug Report or Feature Request (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

1.1.3

Desired functionality.

Angular-cli should support typescript 2.4 (just released yesterday). Right now angular-cli is locked down to max v2.3

[delasteve]

There's an issue with rxjs right now preventing upgrading the CLI to use TypeScript 2.4. I read that the 6.x versions work, but that is in alpha and could lead to some other issues. ⚠️ Use caution if you intend on upgrading early. ⚠️

Expect the CLI to upgrade its dependencies when things are stable again.

Tracking: https://github.com/ReactiveX/rxjs/issues/2539

[moniuch]

@delasteve ...by which issue I was bitten today. And I thought about the following one:
Given that even a minor version release of TypeScript can break things, wouldn't it be wise to generate package json without the ^ character specifically for TS?

[tytskyi]

@moniuch cli already generates package with ~. Looks like people are trying to update it manually or had old package.json

see https://github.com/angular/angular-cli/blob/v1.2.0/packages/%40angular/cli/blueprints/ng/files/package.json#L50

[xnnkmd]

@delasteve @filipesilva RxJS 5.4.2 has now been published with the fix for Typescript 2.4.1

[MarkPieszak]

At least from my testing, if you upgrade rxjs to 5.4.2 you should be able to use the CLI with TS 2.4.

Just remember that you're upgrading at your own risk as I don't believe it has been fully tested &/or is supported at the moment.

[smoke]

I think the referenced issue https://github.com/ReactiveX/rxjs/issues/2539 is now fixed, so are there any plans now?

[OdaiTu]

how to update my typescript to latest version ?
what is the command using npm ?

[jbojcic1]

So is it possible to use typescript >= 2.4 now? I have cli 1.4.6 and it still requires ts < 2.4

[MarkPieszak]

Try CLI 1.5+

[jbojcic1]

@MarkPieszak tried it. I still get the same warning.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}