Warning message is displayed when using TypeScript 2.9.2

[micksatana]

Angular version 6.1.0 support typescript 2.9. But when I change typescript dependency in package.json. This warning is shown.

@angular/compiler-cli@6.1.0 requires typescript@'>=2.7.0 <2.8.0' but 2.9.2 was found instead.
Using this version can result in undefined behaviour and difficult to debug problems.

Please run the following command to install a compatible version of TypeScript.

    npm install typescript@'>=2.7.0 <2.8.0'

To disable this warning run "ng config cli.warnings.typescriptMismatch false".

Bug Report or Feature Request (mark with an x)

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

Command (mark with an x)

- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node --version
v8.9.4

npm --version
6.2.0

ng --version
Angular CLI: 6.1.0
Node: 8.9.4
OS: darwin x64
Angular: 6.1.0
... animations, bazel, cli, common, compiler, compiler-cli, core
... forms, http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.7.0
@angular-devkit/build-angular     0.7.0
@angular-devkit/build-optimizer   0.7.0
@angular-devkit/build-webpack     0.7.0
@angular-devkit/core              0.7.0
@angular-devkit/schematics        0.7.0
@ngtools/webpack                  6.1.0
@schematics/angular               0.7.0
@schematics/update                0.7.0
rxjs                              6.2.2
typescript                        2.9.2
webpack                           4.9.2

Repro steps

1. Create new angular project
   ng new testNg61
2. Change typescript version in package.json to 2.9.2
3. Run npm i
4. Run ng serve

The log given by the failure

@angular/compiler-cli@6.1.0 requires typescript@'>=2.7.0 <2.8.0' but 2.9.2 was found instead.
Using this version can result in undefined behaviour and difficult to debug problems.

Please run the following command to install a compatible version of TypeScript.

    npm install typescript@'>=2.7.0 <2.8.0'

To disable this warning run "ng config cli.warnings.typescriptMismatch false".

Desired functionality

Serve correctly without showing the warning

Mention any other details that might be useful

versionCombos variable in node_modules/@angular/cli/upgrade/version.js seem not being built correctly. The codes in upgrade/version.ts file seem correct.

[gkalpak]

Related: angular/angular#25141

[kylecordes]

As I recall from the last time there was such an upgrade, for various legacy reasons the compatibility version check is implemented in CLI, with the code of that understands the version relationship compiled into CLI (or dev kit). So they will need to be a CLI update to understand that a new range of Angular versions is compatible with the new range of TypeScript versions.

So we are just a bit patient, likely the next new CLI version should understand the new versions, and contain any other needed tweaks to make it all run smoothly.

Is the referenced fix complete? Creating a new project in the CLI, why is the default typescript version set to "~2.7.2" in package.json? Shouldn't it be set to 2.9 by default now or is 2.7 the default for some specific reason?

Tried using latest 6.1.1 update -- same result.

[sarunint]

@sundarchi1 Yes, it does fix the issue when you already upgraded to TypeScript 2.9. The issue you've just raised is a separated issue in which Angular CLI generates TypeScript 2.7 as default.

As for that issue, #11669 is pending.

[micksatana]

@sundarchi1 I tested on my local. the fix is complete. when change version to 2.9.2, no warning display.

[sebek64]

Although this is probably not a big problem, I see that @schematics/angular@0.7.2 still has a dependency on typescript < 2.8. It installs a separate copy of typescript, so it is compatible with global typescript in version 2.9.

[angular-automatic-lock-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.}