Cannot find namespace NodeJS after webpack upgrade

Question

I have Angular2 application that is built with WebPack. I upgraded WebPack from v1.8 to v2, and everything seems to be working fine. The only problem is that the old code has the following:

import Timer = NodeJS.Timer;
....
apptInterval: Timer;
....
this.apptInterval = setInterval(() => { ... }, 1000);

After the upgrade this gives me an error: TS2503: Cannot find namespace 'NodeJS'.

tsconfig.json looks like this:

{
"compilerOptions": {
   "target": "es5",
   "module": "commonjs",
   "moduleResolution": "node",
   "sourceMap": true,
   "emitDecoratorMetadata": true,
   "experimentalDecorators": true,
   "lib": ["es2015", "dom"],
   "noImplicitAny": true,
   "suppressImplicitAnyIndexErrors": true
   }
}

The docs for Angular/Webpack no longer have typings.json; however, even if I copy from Webpack 1 directory, it doesn't help. The content is typings.json is

{
"globalDependencies": {
  "jasmine": "registry:dt/jasmine#2.2.0+20160621224255",
  "node": "registry:dt/node"
  }
}

Interesting that if I remove references to NodeJS, everything works fine. Like this:

apptInterval: any;
....
this.apptInterval = setInterval(() => { ... }, 1000);

If I look under F12 debugger, the type of apptInterval is ZoneTask. I am sure there is a way to make it strong-typed, but it escapes me. The only suggestion I found was to run typings install dt~node --global --save-dev (which essentially updates typings.json, but doesn't help.

i'm using Angular v20 and here you can also set the "apptInterval: ReturnType<typeof setInterval>". this should be a pure typescript definition of the return value of setInterval — Christian M.
– Christian M., Commented Jun 3 at 12:43

Fzum · Accepted Answer · 2017-05-13 11:04:28Z

147

If you also have tsconfig.app.json in your working directory, try to add the attribute node to the types field. Like:

  {
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "outDir": "../out-tsc/app",
    "module": "es6",
    "baseUrl": "",
    "types": ["node"] --> ADD THIS
  },
  "exclude": [
    "test.ts",
    "**/*.spec.ts"
  ]
}

answered May 13, 2017 at 11:04

Fzum

2,1551 gold badge15 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Fzum Over a year ago

@LuigiRubino Glad i could help!

Mill Over a year ago

It also worked for me! Note: it also solved the previous webpack compile error: Cannot find name 'require'. (error ts2304)

AvahW Over a year ago

You can also add types: ["node"] to tsconfig.json, but make sure you don't have an empty types: [] definition in tsconfig.app.json because that overrides it (learned that the hard way...)

Brenton Scott Over a year ago

Could you explain why this is the fix?

Felix Jan 10 at 7:56

@BrentonScott - can you elaborate, what is the question? it is the fix because it fixes the original issue - error: TS2503: Cannot find namespace 'NodeJS'.

|

unional · Accepted Answer · 2022-09-12 05:00:49Z

20

For [email protected]+, use @types:

npm install -D @types/node @types/jasmine

If you still want to hang on to typings, include typings/index.d.ts to your tsconfig.json:

{
  "include": [
    "typings"
  ],
  // or
　"files": [
    "typings/index.d.ts"
  ]
}

edited Sep 12, 2022 at 5:00

answered Mar 22, 2017 at 5:16

unional

15.8k6 gold badges36 silver badges57 bronze badges

4 Comments

Felix Over a year ago

Unfortunately, neither option made any difference.

unional Over a year ago

Open your code in VSCode, and see if NodeJS exists in the intelliSense. It should be there is you have things setup correclty.

TetraDev Over a year ago

Thanks! I forgot to include "**/*.d.ts" in my tsconfig.app.json within the include array. Now my custom type definitions work again.

PiersyP Over a year ago

This did the trick for me!

Deon du Preez · Accepted Answer · 2021-09-14 13:41:58Z

8

I'm running Angular 12 and I have strict mode enabled, I had to add both Fzum and johnny S's answers to my tsconfig.app.json. The only time it didn't throw an error in console is when I had both.

My tsconfig.app.json looks like this:

{
  "compilerOptions":
  {
    ...
    "types": ["node"],
    "typeRoots": [
    "node_modules/@types"
    ]
  }
}

Sorry for making this a separate answer, I don't have enough reputation to comment yet

answered Sep 14, 2021 at 13:41

Deon du Preez

811 silver badge2 bronze badges

Comments

johnny 5 · Accepted Answer · 2019-03-19 23:41:30Z

4

Adding node to the types didn't work for me, "types": ["node"] but adding to the type roots did

{
  "compilerOptions":
  {
    ...
    "typeRoots": [
    "node_modules/@types"
    ]
  }
}

answered Mar 19, 2019 at 23:41

johnny 5

21.2k55 gold badges138 silver badges217 bronze badges

Comments

Luther · Accepted Answer · 2024-06-17 09:39:26Z

0

For me, I had to simply update the zone.js package version to ^0.11.1 and the error disappeared.

answered Jun 17, 2024 at 9:39

Luther

3103 silver badges12 bronze badges

Collectives™ on Stack Overflow

Cannot find namespace NodeJS after webpack upgrade

5 Answers 5

7 Comments

4 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

7 Comments

4 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related