DOM library in not excluded even when lib does not have dom

[quant-daddy]

Bug Report

For a nodejs project, I want to exclude DOM library type definitions. I use the following compiler option

{
  "compilerOptions": {
    "lib": ["es2019", "es2020.promise", "es2020.bigint", "es2020.string"],
    "target": "es2019",
    "module": "commonjs",
    "skipLibCheck": true,
    "moduleResolution": "node",
    "allowSyntheticDefaultImports": true,
    "allowJs": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "inlineSourceMap": true,
    "importHelpers": true,
    "alwaysStrict": true,
    "strict": true,
    "outDir": "build",
    "forceConsistentCasingInFileNames": true,
    "esModuleInterop": true,
    "typeRoots": ["./node_modules/@types", "./typings"],
    "baseUrl": ".",
    "paths": {
      "#root/*": ["./*"]
    }
  },
  "include": [
    "src/**/*",
    "__tests__/**/*",
    "config/**/*",
    "scripts/bundle-test.ts"
  ],
  "exclude": ["node_modules"]
}

I have not included "dom" in the lib options but I am still getting the types from [VS Code installation folder]/code/resources/app/extensions/node_modules/typescript/lib/lib.dom.d.ts] being included in my workspace. This have lead to multiple run time errors. In particular, the parent object from Window is being included (declare var parent: Window;. Is there a way to avoid it?

[RyanCavanaugh]

You can use tsc --explainFiles to see why this file is in your program

[quant-daddy]

Thanks. It turns out there there is a package using lib.dom definition. I ended up using an eslint rule to avoid this issue:

"no-restricted-globals": [
      "error",
      {
        "name": "parent",
        "message": "Do not use window parent"
      },
      {
        "name": "name",
        "message": "Use local parameter instead."
      },
      {
        "name": "event",
        "message": "Use local parameter instead."
      },
      {
        "name": "fdescribe",
        "message": "Do not commit fdescribe. Use describe instead."
      }
    ]

[Soosay86]

https://github.com/vscode-icons/vscode-icons.wiki.git

[bluenote10]

We ran into the same issue. I have analyzed the issue and posted a more refined bug report including a reproduction example here: #43990

[typescript-bot]

This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow.