新创建NestJS项目执行npm run start:dev报TS2430类型错误求助

Hey there, I’ve seen this exact TypeScript type error pop up before in Node.js/backend projects—let’s get your NestJS app running smoothly again!

First, let’s recap the error you’re hitting for clarity:

node_modules/typescript/lib/lib.dom.d.ts:16532:11 - error TS2430 : Interface 'WebGL2RenderingContext' incorrectly extends interface 'WebGL2RenderingContextBase'. Types of property 'clearBufferfv' are incompatible. Type '(buffer: number, drawbuffer: number, values: ArrayLike | Float32Array, srcOffset?: number) => void' is not assignable to type '{ (buffer: number, drawbuffer: number, values: Float32List, srcOffset?: number): void; (buffer: number, drawbuffer: number, values: Iterable, srcOffset?: number): void; }'. Types of parameters 'values' and 'values' are incompatible. Type 'Iterable' is not assignable to type 'ArrayLike | Float32Array'. Type 'Iterable' is missing the following properties from type 'Float32Array': BYTES_PER_ELEMENT, buffer, byteLength, byteOffset, and 25 more.

This issue happens because your project is including browser-specific DOM type definitions (like WebGL) that don’t belong in a Node.js-based NestJS backend. Here are the most straightforward fixes:

Solution 1: Remove DOM Lib from tsconfig.json #

Since NestJS runs on Node.js, you don’t need the browser DOM type definitions. Edit your tsconfig.json file and update the lib array in compilerOptions to remove "dom":

{
  "compilerOptions": {
    // ... other existing settings
    "lib": ["ES2021"], // Remove "dom" from this list
    // ... rest of your config
  }
}

This eliminates the conflicting browser types entirely, which is the cleanest fix for backend projects.

Solution 2: Align Your TypeScript Version #

Sometimes this conflict arises from a mismatch between TypeScript versions and default type definitions. Try installing a stable TS version compatible with your NestJS release (check Nest’s official docs for recommended versions):

npm install typescript@~5.1.6 --save-dev

After updating, restart your dev server with npm run start:dev to see if the error clears up.

Solution 3: Check for Unnecessary Frontend Dependencies #

Double-check that you haven’t accidentally installed any frontend-specific packages (like React, Vue, or browser UI libraries) in your NestJS project. These can pull in DOM type definitions that cause conflicts. If you find any, uninstall them with:

npm uninstall <package-name>

Give these steps a try—Solution 1 is usually the quickest fix for this exact error. Let me know if you run into any other snags!

内容的提问来源于stack exchange，提问作者Tarik Ouhamou