You seem to not be depending on "@angular/core". This is an error

Question

I want to create an angular 2 App with angular cli

I have written in the cmd:

npm install angular-cli -g

then:

ng firstngapp

but it show me an error when I write npm start !

I don't understand the problem

Try to run npm bugs firstngapp and see. It will guide you to resolve your problem — Swanand Taware, Dec 25 '17 at 15:38
Please run "npm update" command. This issue will get when "node_modules" folder missing in your project or only "@angular/core" package missing. — Raju, May 28 '18 at 17:40
After **npm install** you can try closing the project then open again. It worked for me. — Pay, Mar 12 '18 at 09:39
Are you rusty like me? After cloning project... change to project folder and `npm install` — Adam Cox, Apr 09 '18 at 15:36
agreed, you have to run "npm install angular-cli -g ", then "npm install" and finally the "ng XXX" — Andreas Panagiotidis, May 21 '18 at 19:59

score 194 · Answer 1 · edited Apr 06 '23 at 09:54

194

Try to run

npm install

in the project folder (not root folder)

edited Apr 06 '23 at 09:54

Ranjithkumar

16,071
12
120
159

answered Jan 08 '17 at 15:44

galvan

7,400
7
38
55

score 80 · Answer 2 · edited May 29 '18 at 05:16

80

While running ng serve you should be in the app's/project's directory.

If you run the command in another directory you get the error:

You seem to not be depending on "@angular/core". This is an error.

edited May 29 '18 at 05:16

Samuel Liew

76,741
107
159
260

answered Nov 14 '17 at 14:30

niranjan pb

1,125
11
14

2

I was depending on "@angular/core" but i was not in the project directory so i was getting that error – niranjan pb Nov 16 '17 at 02:21

score 16 · Answer 3 · answered Jan 08 '17 at 15:54

16

Delete your node modules , Check your package.json file should have the @angular/core and reinstall it with npm i.

answered Jan 08 '17 at 15:54

SeleM

9,310
5
32
51

score 15 · Answer 4 · edited Nov 22 '17 at 14:33

15

Delete node_modules folder and package-lock.json file.
Then run following command it will update npm packages.

npm update
Later start project executing following command.

ng serve

Above steps worked for me.

edited Nov 22 '17 at 14:33

Dinesh Kumar

307
1
3
9

answered Nov 19 '17 at 09:20

sabin

841
12
15

score 8 · Answer 5 · edited Jun 04 '19 at 17:57

8

Below steps worked for me:

1) Delete the node_modules/ folder and package-lock.json file.

2) npm install

3) ng serve

edited Jun 04 '19 at 17:57

rhavelka

2,283
3
22
36

answered Mar 20 '18 at 16:27

Ashish168

162
4
14

score 8 · Answer 6 · answered Mar 21 '18 at 12:05

8

May help you.

Delete All folders you have created previously
Create fresh folder
Then try navigate to that folder from command "cd foldername"
then try to install "npm install"

This will solve you problem.

answered Mar 21 '18 at 12:05

Ajit Kumar

590
1
8
17

score 7 · Answer 7 · answered Mar 22 '17 at 12:17

7

from terminal

 > cd myProjectPath
 myProjectPath > npm install

answered Mar 22 '17 at 12:17

Pooja

356
2
11

8

This looks very similar to the top answer at the moment - is this a necessary answer? – TerryA Mar 22 '17 at 13:04
1

Better than the same suggestion above. – FeeFiFoFum May 01 '18 at 02:31

Mathias Rodriguez · Answer 8 · 2017-06-23T19:00:41.080

I don't know if it is still an issue. I was experiencing the same nuisance with @angular/cli v1.1.2 on npm 4.1.2. I deleted the node_modules directory and then went on to updating npm (since this was a common cause in the past).

I wanted to upgrade npm to 5.0.3 (latest) but since I was using nvm it seems to have messed up the libraries. Thus, I reinstalled node.

Then, I went with

npm cache clean
npm rebuild
npm install - This one several times, since every time it threw an error with a different package

In the end, every package was fine.

Hope this helps.

score 4 · Answer 9 · answered Mar 05 '18 at 23:55

4

the fix for me was

npm link
ng build

answered Mar 05 '18 at 23:55

grepit

21,260
6
105
81

score 3 · Answer 10 · answered Feb 09 '18 at 15:17

If anyone is running into this in 2018, the thing that finally worked for me was to go into the my-app I created with ng new my-app, and THEN run ng serve This has to do with it needing the dependencies and devDependencies located in my-app/package.json instead of root/package.json. They are two separate files.

Even if I copied the all the dependencies to my root folder's package.json, I would also have to go in and manually change the path locations for the config files and such to go into my-app/*. It is much easier to just go into my-app/ and run ng serve there to let it all work like it is supposed to.

So these steps should work for anyone:

rm -rf <previous-app> // Whatever your previous app was called, if you had one.

sudo rm -rf node_modules

rm -f package-lock.json

npm install

ng new my-app

cd my-app

ng serve

Can you explain what does rm -rf I don't remember if and why I did a `previous-app` After doing your commands I get a `You cannot use the new command inside an Angular CLI project.` error while doing `ng new my-app` — Revolucion for Monica, Apr 04 '18 at 14:05
@Marine1 You cannot create a new Angular app inside of an Angular app. and only run `rm -rf ` if you had a previous app that is creating this problem. substitute the name of you app in here. `rm -rf` _removes recursively by force the entire directory's contents_ — Dan, Apr 18 '18 at 19:49

score 2 · Answer 11 · answered Aug 19 '17 at 13:43

2

Run the npm update after installing all peer dependencies and it will work.

answered Aug 19 '17 at 13:43

Surendra Babu Parchuru

968
1
11
18

score 2 · Answer 12 · edited Apr 06 '19 at 07:06

2

I got the same issue, and the reason is

when you run ng new app-name it will create a new directory with app name and install everything in that.
after running the above command, human tendency is to run ng serve and because your app is in sub directory it will not find package.json and throw the mentioned error.

Solution is pretty simple. just move to the sub directory and then run ng serve

edited Apr 06 '19 at 07:06

Amir

8,821
7
44
48

answered Jan 28 '18 at 14:18

abhirathore2006

3,317
1
25
29

ie., cd ng5 directory – Ajay Takur Mar 28 '18 at 16:36
@AjayTakur directory name will be same as the app name. – abhirathore2006 Mar 29 '18 at 16:56

score 2 · Answer 13 · answered Feb 13 '18 at 22:16

2

Faced the same Issue. While running ngserve you should be in the apps directory. To confirm(on GIT BASH : you will have (master) after the directory path at gitbash prompt, if you are at app directory.)

answered Feb 13 '18 at 22:16

Learner

99
3
14

score 2 · Answer 14 · answered Mar 13 '18 at 21:13

This is how I solved this problem.

I first ran npm install @angular/core.

Then I ran npm install --save.

When both installs had successfully completed I ran npm serve and received an error saying

"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."

I then deleted my node_modules folder as well as my package-lock.json folder.

After I deleted those folders I ran npm install --save once more.

I ran npm start and received another error. This error said Error: Cannot find module '@angular-devkit/core'.

I ran npm install @angular-devkit/core --save.

Finally, I ran npm start and the project started!

Miroslav Jonas · Answer 15 · 2018-01-24T19:57:28.010

1

You create new project with:

ng new firstngapp

In your example you are missing new. This would create folder, generate files and run npm install for you. It seems that you've created folder but there's no Angular CLI app in it.

And for starting the app use:

ng serve

npm start is only used if you have ejected from cli.

edited Jan 24 '18 at 19:57

answered Jan 24 '18 at 19:51

Miroslav Jonas

5,407
1
27
41

score 1 · Answer 16 · answered Mar 14 '18 at 11:06

1

After trying to no avail:

npm install
npm update
ng serve

npm install -g @angular/cli worked for me

answered Mar 14 '18 at 11:06

user3172635

11
3

score 0 · Answer 17 · answered Sep 19 '17 at 07:30

0

I had the same issue and along with removing the node_modules and reinstalling I needed to remove package-lock.json first.

answered Sep 19 '17 at 07:30

RollWhisTler

341
1
3
10

Irshad · Answer 18 · 2017-11-13T19:21:08.110

I was getting the same error when I tried to run "ng serve" after that I saw some suggetions one of the techie told me to update my npm.I did that as well then I got this screen after entering "ng server"

""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_module and package-lock.json(if you have one) and Run npm install again.""

After performing all the actions now its working correctly...and getting message "Compiled Successfully."

score 0 · Answer 19 · answered Dec 12 '17 at 01:34

0

You need to run the ng server from the c:\project\angular-src location. Not just the root of your project.

answered Dec 12 '17 at 01:34

Tony B

41
1
8

OP might not have c:\project\angular-src folder. And no, you answer makes no sense. `ng serve` must be run from the root of the folder, since that's where the `package.json` file defining this script is. – Miroslav Jonas Jan 24 '18 at 19:54

score 0 · Answer 20 · answered Dec 25 '17 at 07:39

0

Executing ng new --skip-install PROJECT_NAME and then manually going into the created folder and typing npm install. https://github.com/angular/angular-cli/issues/3906

answered Dec 25 '17 at 07:39

rsapru

688
14
30

score 0 · Answer 21 · answered Dec 29 '17 at 13:32

0

In my case the following worked:

rm -rf node_modules
rm package-lock.json
npm install

Hence the npm install, not update.

answered Dec 29 '17 at 13:32

Lars

340
4
19

score 0 · Answer 22 · answered Jan 30 '18 at 12:40

The problem I had was that I followed the cli's advice to switch to yarn package management.

Then while following a tutorial I did npm install --save bootstrap, and after that point the error started appearing. Afterwards I did yarn add xxx of course and it worked.

To restore the project's state I removed node_modules and package-lock.json as per this answer and then run yarn install

score 0 · Answer 23 · answered Feb 07 '18 at 12:02

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.

score 0 · Answer 24 · answered Feb 10 '18 at 13:21

This happened to me when I was mixing package managers. My project was generated with Yarn, and after that, I added a couple of dependencies using npm install (this created the package-lock.json with only added dependencies).

Apparently, ng serve used package-lock.json and couldn't find Angular dependencies there. After I started using only Yarn, i.e. yarn add instead of npm install, the error was gone.

score 0 · Answer 25 · edited May 29 '18 at 05:14

For ng serve you need to be inside that directory

ashish@ashish-Inspiron-3521:~/Angular$ ng new FireStore
  create FireStore/README.md (1025 bytes)
  create FireStore/.angular-cli.json (1245 bytes)
  create FireStore/.editorconfig (245 bytes)
  create FireStore/.gitignore (544 bytes)
  create FireStore/src/assets/.gitkeep (0 bytes)
  create FireStore/src/environments/environment.prod.ts (51 bytes)
  create FireStore/src/environments/environment.ts (387 bytes)
  create FireStore/src/favicon.ico (5430 bytes)
  create FireStore/src/index.html (296 bytes)
  create FireStore/src/main.ts (370 bytes)
  create FireStore/src/polyfills.ts (3114 bytes)
  create FireStore/src/styles.css (80 bytes)

ashish@ashish-Inspiron-3521:~/Angular$ ng serve
You seem to not be depending on "@angular/core". This is an error.

How I solved this using cmd

ashish@ashish-Inspiron-3521:~/Angular$ cd FireStore/

Now Do cmd

ashish@ashish-Inspiron-3521:~/Angular/FireStore$ ng serve
** NG Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

score 0 · Answer 26 · answered Apr 26 '18 at 10:42

**You should be in the newly created YOUR_APP folder before you hit the ng serve command **

Lets start from fresh,

1) install npm

2) create a new angular app ( ng new <YOUR_APP_NAME> )

3) go to app folder (cd YOUR_APP_NAME)

4) ng serve

I hope it will resolve the issue.

score 0 · Answer 27 · edited May 29 '18 at 05:12

0

To solve this problem.

Step1: cd projectName
Step2: npm update
Step3: ng serve -o

For example :

edited May 29 '18 at 05:12

Samuel Liew

76,741
107
159
260

answered May 29 '18 at 05:09

BehrouzMoslem

9,053
3
27
34

You seem to not be depending on "@angular/core". This is an error

27 Answers27

Linked

Related