-
Notifications
You must be signed in to change notification settings - Fork 12.8k
DOM library in not excluded even when lib does not have dom #43929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
You can use |
Thanks. It turns out there there is a package using lib.dom definition. I ended up using an eslint rule to avoid this issue:
|
We ran into the same issue. I have analyzed the issue and posted a more refined bug report including a reproduction example here: #43990 |
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. |
Bug Report
For a nodejs project, I want to exclude DOM library type definitions. I use the following compiler option
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, theparent
object fromWindow
is being included (declare var parent: Window;
. Is there a way to avoid it?The text was updated successfully, but these errors were encountered: