Build:Cannot find type definition file for 'node'

Question

VS 2015 community edition (at home), npm 3.10, Angular 2 Im trying to pull get Angular2 setup within an ASP.Net MVC 5 app. The template I started with used an older version of Angular, so I updated the package references.

When I build, the first error in the list is:
Build:Cannot find type definition file for 'node'
There are dozens of other errors after that but Im assuming most are due to this first issue.

Here is the package.json and typings.json

package.json

{
  "version": "1.0.0",
  "name": "aspnet",
  "private": true,
  "scripts": {
    "postinstall": "typings install",
    "typings": "typings"
  },
  "dependencies": {
    "@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",
    "angular-in-memory-web-api": "~0.3.0",
    "systemjs": "0.19.40",
    "core-js": "^2.4.1",
    "rxjs": "5.0.1",
    "zone.js": "^0.8.4",
    "bootstrap": "^3.3.7"
  },
  "devDependencies": {
    "@types/core-js": "^0.9.41",
    "gulp": "^3.9.1",
    "gulp-clean": "^0.3.2",
    "gulp-concat": "^2.6.1",
    "gulp-tsc": "^1.3.1",
    "gulp-typescript": "^3.1.6",
    "path": "^0.12.7",
    "typescript": "~2.1.0",
    "typings": "~2.1.1"
  }
}

typings.json

{
  "globalDependencies": {
    "core-js": "registry:dt/core-js#0.0.0+20160725163759",
    "jasmine": "registry:dt/jasmine#2.2.0+20160621224255",
    "node": "registry:dt/node#6.0.0+20160909174046"
  }
}

If I try to update just the typings, I get these messages

*typings WARN deprecated 11/21/2016: "registry:dt/node#6.0.0+20160909174046" is deprecated (updated, replaced or removed)
typings WARN deprecated 9/14/2016: "registry:dt/core-js#0.0.0+20160725163759" is deprecated (updated, replaced or removed)
typings WARN deprecated 10/25/2016: "registry:dt/jasmine#2.2.0+20160621224255" is deprecated (updated, replaced or removed)*

[ update ]
cleaning out my node_modules folder, then running npm install again cleared things up. This seems to happen most often when I move a project folder to another location on my system.

Try to install the latest LTS Node.js version first, it might be an outdated Node version. Also, I think typings are deprecated. — Alex Beugnet, Apr 21 '17 at 13:50

score 200 · Answer 1 · edited Nov 01 '19 at 13:21

200

In my case, I solved my problem. Hopefully it helps some else later.

npm install @types/node --save-dev

edited Nov 01 '19 at 13:21

Code Whisperer

22,959
20
67
85

answered Aug 22 '17 at 06:36

M2012

3,465
2
20
27

1

should be --save-dev. How come microsoft's node project template is missing it? Don't they test their stuff? – Mikser Nov 09 '18 at 14:08
1

This answer solved things for me right away,including for a nested project – Code Whisperer Nov 01 '19 at 13:21
Adding the same for @types/jasmine and @types/jasminedw2 also resolve similar errors for those packages. (Using TypeScript 2.0 without NuGet in Visual Studio 2019!) – Sorin Dolha Dec 09 '20 at 13:09
@Mikser why should it be --save-dev? Doesn't this library contain only compile-time structures? I mean there might be no difference – Enbugger Dec 15 '20 at 21:44
1

@xotonic, It actually depends on the way your project is built and run. One might need an optimized production build without devDependencies modules that take up extra space. – Mikser Dec 19 '20 at 13:16
Can you explain what it install exactly – Bob the Builder Sep 07 '22 at 00:39
1

@BobtheBuilder it will install the typescript definitions for the Node.js runtime as dev dependency(use --save-dev flag with npm install) and its modules. – Rahul Feb 24 '23 at 07:21

score 39 · Accepted Answer · edited Feb 14 '19 at 13:54

39

I had several problems updating packages through visual studio. From now i always update or add packages with the powershell console.

Start PowerShell and navigate to the folder where package.json is located and then run npm install Restart visual studio after the installation is done.

You can also try to delete your node_modules folder then run npm install

Hope this will solve your problems.

edited Feb 14 '19 at 13:54

jithinkmatthew

890
8
17

answered Apr 21 '17 at 18:50

argoo

1,428
12
17

2

I just had this problem and just running npm install fixed it – N8ALL3N May 15 '18 at 18:58
1

Side node, this is still true for vs2019. I tried using the package manager console to run `npm install` but that also did not work, i really had to go open cmd and run it there for it to work. – sommmen Jul 01 '20 at 10:40
npm install with PS is wwwayyyyy slower, just a tip. Use simple command line or bash. – Kat Lim Ruiz Jun 01 '21 at 17:08
Restarting vscode was a necessary step for me on Windows. Thanks. – Victor Eke Apr 26 '23 at 10:46

score 32 · Answer 3 · answered Jun 23 '21 at 06:25

32

Restarting or reloading my VSCode worked

answered Jun 23 '21 at 06:25

Albert

501
4
7

1

This seemed like a long shot, but it actually worked! – Rafael Marques Dec 15 '21 at 11:57
His using Visual Studio, Not VS Code. – Syska Jan 08 '22 at 00:38

score 4 · Answer 4 · answered Feb 22 '21 at 10:04

4

sometimes its just because some package(s) are missing. you can try running yarn install or npm install should resolve.

answered Feb 22 '21 at 10:04

aatif shaikh

673
10
18

score 4 · Answer 5 · edited Mar 23 '23 at 17:20

4

On my end, this was an issue with the TS server in VSCode. You can simply restart the server by:

Opening any TS file > CMD + SHIFT + P > TypeScript: Restart TS Server

edited Mar 23 '23 at 17:20

Tyler2P

2,324
26
22
31

answered Mar 17 '23 at 20:41

mogcast

41
2

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

For local Visual Studio

If you're starting with a clean template the build in VS functionality should probably work!

Go to Dependencies > npm > Right Click > Restore Packages

Then try build again.

For Visual Studio Team Services

Install node https://nodejs.org/en/download/
Restart your agent service (VSTS Agent) if not using hosted agents
Add a build task to run npm install
Click the menu icon next to 'Working folder' to choose the location where your project.json file is located.

score 2 · Answer 7 · edited May 06 '21 at 08:44

2

The easiest way to go around this in vscode is.

create a .vscode directory, then inside it, create settings.json and put the below json and you are good to go.

{
"search.exclude": {
  "**/node_modules": true
},
"files.watcherExclude": {
  "**/.git/objects/**": true,
  "**/.git/subtree-cache/**": true,
  "**/node_modules/**": true,
  "env-*": true
},
"files.exclude": {
  "**/.git": true,
  "**/.DS_Store": true,
  "**/node_modules": true,
  "env*": true
}
}

edited May 06 '21 at 08:44

E_net4

27,810
13
101
139

answered May 05 '21 at 19:53

Sodruldeen Mustapha

1,135
10
22

His using Visual Studio, Not VS Code. – Syska Jan 08 '22 at 00:38

score 2 · Answer 8 · answered Feb 19 '23 at 21:09

2

Restart Typescript or re-open vscode worked for me

answered Feb 19 '23 at 21:09

Radmehr

299
2
12

score 1 · Answer 9 · answered Jan 22 '20 at 07:02

1

Problem can be around other issues as well

Try one of the step of the solution posted here Cannot find type definition file for 'node' by me

answered Jan 22 '20 at 07:02

TARJU

1,785
1
14
16

score 0 · Answer 10 · answered Jan 06 '22 at 02:08

0

I had this problem when i've been working with RN and i put a incorrect dependency on my package.

    "@types/": "react-navigation/native",

react-navigation/native don't exists

json

When i tried run tsc with it, i got this

answered Jan 06 '22 at 02:08

Jackson Smith

576
4
14

score 0 · Answer 11 · answered Apr 12 '23 at 07:45

0

for rocketchat apps, this should fix the problem:

npm link @types/node

answered Apr 12 '23 at 07:45

Tiana987642

696
2
10
28

Build:Cannot find type definition file for 'node'

11 Answers11

For local Visual Studio

For Visual Studio Team Services

Linked