typescript error - cannot find name 'process'

Question

I am setting up a new project with express+ typescript and facing typescript error - cann't find name 'processs'

package.json

"dependencies": {
    "express": "^4.16.4",
    "nodemon": "^1.18.7",
    "tsc": "^1.20150623.0",
    "typescript": "^3.1.6"
  },
  "devDependencies": {
    "@types/express": "^4.16.0",
    "@types/mocha": "^5.2.5",
    "@types/node": "^10.12.10",
    "eslint": "^5.9.0",
    "eslint-config-airbnb-base": "^13.1.0",
    "eslint-plugin-import": "^2.14.0",
    "eslint-plugin-promise": "^4.0.1",
    "mocha": "^5.2.0",
    "supertest": "^3.3.0",
    "typescript-eslint-parser": "^21.0.1"
  }

I tried to follow the solution and added types tsconfig

{
    "compilerOptions": {
      "target": "es6",
      "module": "commonjs",
      "outDir": "dist",
      "sourceMap": true,
      "types": ["node"] -----
    },
    "include": [
      "src/**/*.ts"
    ],
    "exclude": [
      "node_modules"
    ]
}

But I still get the error. I have installed npm (6.4.1) and node (8.14.0) to start building up my new project. Can someone highlight what I am doing wrong?

fix · Accepted Answer · 2021-09-28 13:00:50Z

147

Make sure you have "types": ["node"] in your tsconfig.app.json file. Having it in tsconfig.json was not enough for me (Angular 12).

{
  ...
  "compilerOptions": {
    ...
    "types": ["node"]
  },
 ...
}

answered Sep 28, 2021 at 13:00

fix

2,2752 gold badges21 silver badges30 bronze badges

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

2 Comments

chick3n0x07CC Over a year ago

This helped me with Vue 3 + Vite.

Gert Rikkers Over a year ago

This was also very helpful to me when using Vue 3 + Vite. It even works when omitting this option in 'tsconfig.config.json': I only had to add this compiler option in the file 'tsconfig.json'

Alex Yatkevich · Accepted Answer · 2018-11-29 02:30:44Z

91

Your new configuration looks right. Although, you probably have to restart typescript language server if it still uses previous version of the tsconfig. In order to do this in VS Code, you do Ctrl+Shift+P and Reload Window or TypeScript: Restart TS server if available.

Also you don't need tsc package in your dependencies, because it is deprecated now, and typescript package comes with tsc executable.

edited Nov 29, 2018 at 2:30

answered Nov 28, 2018 at 23:21

Alex Yatkevich

1,46411 silver badges11 bronze badges

4 Comments

devklick Over a year ago

Just to point out that it's the @types/node dev dependency that seems to be required to fix this issue. At least, that's what got rid of the error for me.

igneosaur Over a year ago

You may also need a tsconfig.json file typescriptlang.org/docs/handbook/tsconfig-json.html

netotz Over a year ago

I did yarn add -D @types/node, then I restarted the TS server, and now it works. I don't have a tsconfig.json, using Node.js v18.9.0

DaveDean1 Aug 5 at 15:48

For people coming at this from React/Vite: The tsconfig + Restart TS Server hint will be good for a lot of people

Steven Almeroth · Accepted Answer · 2022-09-18 02:46:28Z

55

Just to point out that it's the @types/node dev dependency that seems to be required to fix this issue. At least, that's what got rid of the error for me. – devklick Jul 8 at 8:42

Using npm:

npm i --save-dev @types/node

Using Yarn: (@netotz)

yarn add -D @types/node

edited Sep 18, 2022 at 2:46

answered Oct 7, 2021 at 19:45

Steven Almeroth

8,2522 gold badges54 silver badges60 bronze badges

2 Comments

plutownium Over a year ago

Following this yielded

npm ERR! 404  '@typescript-eslint/type-utils@https://registry.npmjs.org/@typescript-eslint/types-utils/-/types-utils-5.19.0.tgz' is not in the npm registry.

netotz Over a year ago

yarn add -D @types/node

David Carboni · Accepted Answer · 2022-07-29 16:00:31Z

12

I got the error in /test/*.spec.ts files only.

I didn't want to add @types/node to my main dependencies.

For me, updating my tsconfig.json as follows fixed it:

  "include": [
    "src/**/*.ts",
    "test/**/*.spec.ts"
  ],

answered Jul 29, 2022 at 16:00

David Carboni

2,2862 gold badges30 silver badges31 bronze badges

1 Comment

Sathish K M Sep 22 at 6:32

Thanks, my file was outside src, moving it inside src fixed the issue.

Turtlepaw · Accepted Answer · 2024-09-23 19:21:15Z

4

I got this issue today. I had a drizzle.config.ts in the root folder that wasn't included in tsconfig.json.

Update the includes in tsconfig.json

{
   // ...
   "include": ["src/**/*.ts", "*.ts"], // Add every .ts file in the root directory
}

edited Sep 23, 2024 at 19:21

Turtlepaw

6555 silver badges20 bronze badges

answered Sep 21, 2024 at 20:50

arxxanDarkknight

315 bronze badges

1 Comment

user30482 Jan 25 at 19:34

Similar issue here. If the problem occurs in a subdirectory of "src/", then the recursive pattern "src/**/*.ts" is missing. Alternatively, if access to node.js types is needed in only one file, one can add an import: import "node"; in that file.

JHannes · Accepted Answer · 2024-06-15 08:38:00Z

2

For me this error occurred in the playwright.config.ts file. To fix it I had to add this file to the "include" option in my tsconfig.node.json like so:

{
  "compilerOptions": {
    "composite": true,
    "skipLibCheck": true,
    "module": "es2022",
    "moduleResolution": "bundler",
    "allowSyntheticDefaultImports": true
  },
  "include": ["vite.config.ts", "playwright.config.ts"]
}

Then restart the TS Server in VSCode (see other comment here) and the error was gone.

To sum up: When you see the typescript error Cannot find name 'process' in a file then it is probably not covered by your TS compiler (included in your tsconfig).

answered Jun 15, 2024 at 8:38

JHannes

1,4832 gold badges10 silver badges12 bronze badges

Comments

Jose Rafael Mendes Barbosa · Accepted Answer · 2022-06-16 12:37:31Z

1

Here I had a similar issue, that the --save-dev didnt work, so I would say add the @types/node as a normal dependency instead of a dev one.

answered Jun 16, 2022 at 12:37

Jose Rafael Mendes Barbosa

754 bronze badges

3 Comments

A1rPun Over a year ago

You don't need types as dependency because you only use it while developing hence why it's in devDependencies.

GolDDranks Over a year ago

@A1rPun but this indeed fixed my problem too. It works when I run it, but for some reason, VS Code type errors unless the types are not in dependencies.

Jose Rafael Mendes Barbosa Over a year ago

@GolDDranks I think that worked for you as when we are adding on dependecies we can do npm install, and this will be installed on node_modules, if the type isn't on node_modules would be hard to use them. I would say if you want to add as devDependecies you also need to install: npm install --only=dev I think after this you will be able to make it work as devDependecy. I hope this helps!

Mehdi Benhamouche · Accepted Answer · 2024-09-14 09:39:11Z

0

angular 16 (local). This works for me instead of adding 'node' in 'compilerOptions' types.

 "angularCompilerOptions": {
        "types": ["node"],
    ...
    }

answered Sep 14, 2024 at 9:39

Mehdi Benhamouche

1091 silver badge4 bronze badges

Comments

Talanted Vu · Accepted Answer · 2025-01-07 17:57:19Z

0

If you are using Vite + Vue 3 + Typescript. Create such .env file in the root of your project (prefix VITE for vars is mandatory):

VITE_MY_VAR=MY_VAL_1

Then use such code in your vue app:

const myVar1 = import.meta.env.VITE_MY_VAR;
alert(myVar1)

And you dont need to install @types/node. You dont need to edit tsconfig.

answered Jan 7 at 17:57

Talanted Vu

1392 silver badges6 bronze badges

Collectives™ on Stack Overflow

typescript error - cannot find name 'process'

9 Answers 9

2 Comments

4 Comments

2 Comments

1 Comment

1 Comment

Comments

3 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

9 Answers 9

2 Comments

4 Comments

2 Comments

1 Comment

1 Comment

Comments

3 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related