"You seem to not be depending on "@angular/core"."
When I try to build my project running the following command:
ng build --environment=prod --aot=false --output-path="..." --base-href="..."
You seem to not be depending on @angular/core.
This is an error, however, I don't understand why because before it worked well.
I tried to do this:
npm install @angular/core
But I get this error :
error at Error (native) error { Error: EACCES: permission denied, chown '' error at Error (native) error errno: -13, error code: 'EACCES', error syscall: 'chown', error Please try running this command again as root/Administrator. verbose exit [ -13, true ]
I also tried to get rid of node_modules, then make an install npm: but I get the same error.
And when I run the following command:
ng serve
I have another error:
The "@angular/compiler-cli" package was not properly installed. Error: Error: Cannot find module '@angular/compiler-cli'
This is my package.json :
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
"@angular/animations": "^4.0.0",
"@angular/common": "^4.0.0",
"@angular/compiler": "^4.0.0",
"@angular/core": "^4.0.0",
"@angular/forms": "^4.0.0",
"@angular/http": "^4.0.0",
"@angular/platform-browser": "^4.0.0",
"@angular/platform-browser-dynamic": "^4.0.0",
"@angular/router": "^4.0.0",
"@types/jquery": "^3.2.17",
"cli-color": "^1.2.0",
"core-js": "^2.4.1",
"font-awesome": "^4.7.0",
"jquery": "^3.2.1",
"matrix-js-sdk": "^0.8.5",
"moment": "^2.18.1",
"olm": "https://matrix.org/packages/npm/olm/olm-2.2.2.tgz",
"readline": "^1.3.0",
"rxjs": "^5.4.1",
"socket.io-client": "^2.0.3",
"zone.js": "^0.8.14"
"@angular/cli": "1.2.6",
"@angular/compiler-cli": "^4.0.0",
"@angular/language-service": "^4.0.0",
"@types/jasmine": "~2.5.53",
"@types/jasminewd2": "~2.0.2",
"@types/jquery": "^3.2.17",
"@types/node": "~6.0.60",
"codelyzer": "~3.0.1",
"jasmine-core": "~2.6.2",
"jasmine-spec-reporter": "~4.1.0",
"karma": "~1.7.0",
"karma-chrome-launcher": "~2.1.1",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.2.1",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.1.2",
"ts-node": "~3.0.4",
"tslint": "~5.3.2",
"typescript": "~2.3.3"
Solution 1:
Not sure whether below approach will solve your problem or not, please try once.
I have also faced the same issue while executing below command.
D:\My_Project>ng serve
Then I have followed below steps and it worked for me.
D:\My_Project>npm link
D:\My_Project>ng serve
If this is not working kindly let me know I will try to reproduce the error which you are getting and try to give you solution as soon as possible.
Solution 2:
How to use
Run npm install inside this project folder to install all dependencies.
Make sure you use the latest version of the CLI (upgrade guide below)
Run ng serve to see the app in action (try npm start in case ng serve fails).
How to upgrade the CLI
Run the below commands - only use "sudo" on Mac/ Linux.
sudo npm uninstall -g angular-cli @angular/cli
npm cache clean --force
sudo npm install -g @angular/cli
In case it fails
Delete node_modules folder and package-lock.json file from your project directory
Run the below commands in the given order-
npm install
npm install --save-dev @angular-devkit/build-angular
npm link
Solution 3:
I went down the list of installing the various dependencies as prompted in the terminal. I am running on Windows so I also installed windows Build Tools.
I ran ng serve and got "You seem to not be depending on "@angular/core" and/or "rxjs". This is an error."
Then ran
npm link
followed by
ng serve
Everything is now running. Not sure how much of what I did was necessary/redundant but I can now build Angular projects.
Solution 4:
Faced the same issue and solved by executing the npm link command.
When we run
npm linkin a module’s root directory, npm creates a symbolic link from our “global node_modules” directory to the local module’s directoryThe “global node_modules” directory is a special directory where all modules installed with
npm install -gare stored. We can find the path to our global node_modules directory by runningnpm root -g
Visit :- https://medium.com/@alexishevia/the-magic-behind-npm-link-d94dcb3a81af
Solution 5:
Stupid fix
Removing node_modules and installing the packages again npm i or yarn worked for me!