Versions of @angular/compiler-cli and typescript could not be determined.
See original GitHub issueBug Report or Feature Request (mark with an x
)
- [x] bug report -> please search issues before submitting
- [ ] feature request
Versions.
ng 1.5.0 node 8.9.0 npm 5.5.1 yarn 1.3.2 visual studio code 1.17.2
Repro steps.
run ng serve or ng serve -aot
The log given by the failure.
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.
Desired functionality.
Mention any other details that might be useful.
here my package.json
{
"name": "migate",
"version": "0.1.0",
"license": "MIT",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"@angular/animations": "^5.0.0",
"@angular/common": "^5.0.0",
"@angular/core": "^5.0.0",
"@angular/forms": "^5.0.0",
"@angular/platform-browser": "^5.0.0",
"@angular/platform-browser-dynamic": "^5.0.0",
"@angular/router": "^5.0.0",
"bootstrap": "^4.0.0-beta.2",
"core-js": "^2.5.1",
"global": "^4.3.2",
"jquery": "^3.2.1",
"json-typescript-mapper": "^1.1.3",
"popper.js": "^1.12.6",
"roboto-fontface": "^0.8.0",
"rxjs": "^5.5.2",
"typescript-string-operations-ng4": "^0.1.0",
"zone.js": "^0.8.18"
},
"devDependencies": {
"@angular/cli": "^1.5.0",
"@angular/compiler": "^5.0.0",
"@angular/compiler-cli": "^5.0.0",
"@angular/language-service": "^5.0.0",
"@types/jasmine": "~2.6.2",
"@types/jasminewd2": "~2.0.3",
"@types/node": "~8.0.47",
"codelyzer": "~4.0.0",
"jasmine-core": "~2.8.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~1.7.1",
"karma-chrome-launcher": "~2.2.0",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.3.0",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.2.0",
"ts-node": "~3.3.0",
"tslint": "~5.8.0",
"typescript": "~2.4.0",
"webpack": "^3.8.1",
"webpack-sources": "^1.0.1"
}
}
Issue Analytics
- State:
- Created 6 years ago
- Reactions:13
- Comments:42 (3 by maintainers)
Top Results From Across the Web
Versions of @angular/compiler-cli and typescript could not be ...
Versions of @angular/compiler-cli and typescript could not be determined. The most common reason for this is a broken npm install. Please make ...
Read more >Versions of @angular/compiler-cli and typescript ... - iTecNote
determined. The most common reason for this is a broken npm install. ... package-lock.json (if you have one) and run npm install again....
Read more >@angular/compiler-cli - npm
Angular - the compiler CLI for Node.js. Latest version: 15.0.4, last published: 11 days ago. Start using @angular/compiler-cli in your ...
Read more >versions of @angular/compiler-cli and typescript could not be ...
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...
Read more >How To Update Angular CLI To Latest Version
After updating Angular CLI globally you might get this warning if your local project's angular cli version less than the global angular cli...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I solved The Issue after 23hrs of research and continues trails
Sollution:
Add the three { “@angular/cli”: “1.5.2”, “@angular/compiler-cli”: “^5.0.0”, “typescript”: “^2.4.2” } in “dependencies” too so these will be installed without error I repeat again make sure the above three are available in “dependencies” and Devdependencies too…
It will work for sure… If you have any doubts mail me or call me
Thank you, everyone…
I don’t have NODE_ENV=production and have the same error