Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Angular cli 1.6 and Typescript 2.5.3 warning

See original GitHub issue

I’ve recently updated to Angular 5.1.0 and Angular CLI 1.6.0 which is supposed to be typescript 2.5 friendly however I’m receiving the following warning

@angular/compiler-cli @5.1.0 requires typescript@‘>=2.4.2 <2.5.0’ but 2.5.3 was found instead.

Versions

Angular CLI: 1.6.0
Node: 7.9.0
OS: win32 x64
Angular: 5.1.0
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router

@angular/cli: 1.6.0
@angular-devkit/build-optimizer: 0.0.35
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.41
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0
@schematics/angular: 0.1.10
@schematics/schematics: 0.0.10
typescript: 2.5.3
webpack: 3.10.0

  "dependencies": {
    "@angular/animations": "^5.1.0",
    "@angular/common": "^5.1.0",
    "@angular/compiler": "^5.1.0",
    "@angular/core": "^5.1.0",
    "@angular/forms": "^5.1.0",
    "@angular/http": "^5.1.0",
    "@angular/platform-browser": "^5.1.0",
    "@angular/platform-browser-dynamic": "^5.1.0",
    "@angular/platform-server": "^5.1.0",
    "@angular/router": "^5.1.0",
    "core-js": "^2.5.1",
    "rxjs": "^5.5.5",
    "zone.js": "^0.8.18"
  },
  "devDependencies": {
    "@angular/cli": "^1.6.0",
    "@angular/compiler-cli": "^5.1.0",
    "@types/jasmine": "2.5.38",
    "@types/node": "^6.0.92",
    "codelyzer": "~3.0.1",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "^1.7.1",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "^1.1.1",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.1.2",
    "ts-node": "~3.0.4",
    "tslint": "~5.3.2",
    "typescript": "~2.5.0"
  }

Repro steps

ng serve --aot

Issue Analytics

State:
Created 6 years ago
Reactions:25
Comments:8 (3 by maintainers)

Top GitHub Comments

10reactions

kylecordescommented, Dec 11, 2017

Is there some way to make CLI not add its own additional requirement on top of what the underlying package requires? It was pointed out over in the Angular repo that the Angular package already has the correct dependency. I’d rather see CLI just accept the upstream requirement from Angular itself, rather than have things like this that have to be changed to match Angular, if possible?

9reactions

brian428commented, Dec 8, 2017

In case the team isn’t aware, TS is already up to 2.6.2. So even expanding the peer dependency range to <2.6 is already outdated. So the range probably should become <2.7?

Top Results From Across the Web

angular/cli and typescript version compilation error

So, I change my typescript version to 2.5.3 but now I have compilation error, wich I haven't when cli and typescript versions didn't...

How To Update Angular CLI To Latest Version

To update Angular CLI to latest version Angular, use ng update @angular/core @angular/cli@latest command.

to disable this warning use ng config -g cli.warnings ... - You.com

It just means that you have installed the Angular CLI globally and locally (once using npm install -g and once using just npm...

angular/angular-cli - Gitter

Please run the following command to install a compatible version of TypeScript. npm install typescript@'>=2.1.0 <2.4.0'. To disable this warning run "ng set ......

ng build -prod error when compiling scss - MDBootstrap

Use Container#append any known compatibility issues or fixes for this, thanks here is my setup Angular CLI: 1.6.5 Node: 7.8.0 OS: darwin x64...