Versions of @angular/compiler-cli and typescript could not be determined

Question

I have installed Angular/cli and then try to run command ng serve then below error is throwing. I have tried lot of thing like uninstall angular/cli, npm cache clean, etc

Versions of @angular/compiler-cli and typescript could not be determined. The most common reason for this is a broken npm install.

Please make sure your package.json contains both @angular/compiler-cli and typescript in devDependencies, then delete node_modules and package-lock.json (if you have one) and run npm install again.

Yeah I tried solution with versions change then it is worked for me. — Harshad Kumbhar, Apr 03 '18 at 15:57

score 18 · Answer 1 · edited May 24 '18 at 15:55

18

This may be a problem in not implicitly running devDependencies.

Try running them implicitly with the command below.

npm install --dev

edited May 24 '18 at 15:55

Xatenev

6,383
3
18
42

answered Nov 24 '17 at 02:45

Cixtian Trybe

181
2

Ok will check this one. – Harshad Kumbhar Nov 24 '17 at 09:25
5

install Usage of the `--dev` option is deprecated. Use `--only=dev` instead. – N.K Feb 22 '18 at 09:08

Iancovici · Answer 2 · 2017-12-01T12:08:37.340

5

Generic way out to escape this issue

Create a new project

ng new angular-seed
Copy all the default dependencies and dev-dependenices from package.json to your current project in use (angular, typescript, etc...)

Then remove node_modules and run install npm packages of your current project, or whatever method you use to reubild

rm -fr node_modules npm install

note: if this doesn't get you the latest version, then you may have global tools installed in roaming data (in window explored browser type %appdata%, and navigate to npm to observe)

edited Dec 01 '17 at 12:08

answered Dec 01 '17 at 12:02

Iancovici

5,574
7
39
57

I find this generic method useful for solving many Angular problems, including problems with upgrades. – John Pankowicz Sep 15 '19 at 00:14

score 3 · Answer 3 · edited Jun 20 '20 at 09:12

3

1. Open the command prompt in your project folder.

2. Run the command.

 npm install --only=dev

edited Jun 20 '20 at 09:12

Community

1
1

answered Apr 02 '18 at 09:07

Deepu Reghunath

8,132
2
38
47

score 2 · Answer 4 · answered Nov 26 '17 at 09:46

By default, npm install will install all modules listed as dependencies. With the --production flag, npm will not install modules listed in devDependencies. either we can go

First Way

for editing the dependency part in package.json by adding it with relevant version

    "dependencies": {
    /*existing part */

     "@angular/cli": "1.5.2",
    "@angular/compiler-cli": "^5.0.0",
    "typescript": "^2.4.2"
    }

Second Way

To install dev dependencies, npm --production=false install will work even with NODE_ENV=production.

Or you can run NODE_ENV=development npm install

for more details click to know more

score 2 · Answer 5 · edited Feb 04 '18 at 01:35

2

In the case of deployment, it is a good idea to add a preinstall script to address these gaps in dependencies:

"preinstall": "npm install @angular/cli @angular/compiler-cli typescript"

edited Feb 04 '18 at 01:35

סטנלי גרונן

2,917
23
46
68

answered Feb 03 '18 at 22:51

Zack Biernat

53
6

score 2 · Answer 6 · answered Sep 11 '18 at 05:23

2

First, for prevent, update angular

npm install -g @angular/cli

Second, also the run "npm install", you must install dev dependencies

npm install --dev

verify dependencies are without error

ng --version

answered Sep 11 '18 at 05:23

Diego Santa Cruz Mendezú

4,325
39
27

score 0 · Answer 7 · answered Nov 16 '17 at 11:27

0

Could you check that your "@angular/compiler" in your dependencies is compatible with angular/cli version.

For example :

  "devDependencies": {
    "@angular/cli": "1.4.8",
    "@angular/compiler-cli": "4.4.6",

is compatible with :

"@angular/compiler": "4.4.6",

answered Nov 16 '17 at 11:27

Dali Grissa

51
1
2
10

i had the same issue. i made sure compiler and compiler-cli are in the same version, but issue still exists. – Alex W. Nov 17 '17 at 04:13
Yes I have the DevDependencies like below "devDependencies": { "@angular/cli": "1.4.2", "@angular/compiler-cli": "^4.2.4", – Harshad Kumbhar Nov 17 '17 at 17:48

score 0 · Answer 8 · edited Apr 12 '18 at 19:33

0

Please run the command

npm --production=false install

in your terminal. Also note that you should be in your project folder while executing this.

edited Apr 12 '18 at 19:33

rollstuhlfahrer

3,988
9
25
38

answered Apr 12 '18 at 19:31

Atikant

1

score 0 · Answer 9 · edited May 24 '18 at 17:56

Actually the real problem is with npm.

If its downloading as --legacy-bundling=true (Which is by default) then you will have this issue. If you see node_modules folder all the dependent modules would be nested.

When you run npm install command you should set --legacy-bundling=false

npm install --legacy-bundling=false

Now if you see node_modules folder no any module would be nested. And everything will work.

You can set npm default behaviour using following command, then you will not have to set every time.

npm set --legacy-bundling=false

score 0 · Answer 10 · answered Feb 02 '19 at 01:06

I came across this issue when I was installing npm dependencies on Jenkins. I had @angular/compiler-cli in devDependencies and typescript in dependencies and NODE_ENV=production in the environment.

I tried NODE_ENV=development npm install and it worked for me.

For more details see this : https://github.com/angular/angular-cli/issues/8407

Murat Yıldız · Answer 11 · 2023-02-07T21:20:49.343

0

Also check these dependencies package.json:

...
"@angular/cli": "x.x.x",
"@angular/compiler": "^y.y.y",
"@angular/compiler-cli": "^z.z.z",
"typescript": "^t.t.t"
...

edited Feb 07 '23 at 21:20

answered Feb 15 '19 at 07:43

Murat Yıldız

11,299
6
63
63

Versions of @angular/compiler-cli and typescript could not be determined

11 Answers11

1. Open the command prompt in your project folder.

2. Run the command.

Linked