Skip to content

Don't replace Node and Element types with any#61

Open
jespertheend wants to merge 2 commits intolucacasonato:mainfrom
jespertheend:lib-dom-types
Open

Don't replace Node and Element types with any#61
jespertheend wants to merge 2 commits intolucacasonato:mainfrom
jespertheend:lib-dom-types

Conversation

@jespertheend
Copy link

I'm not sure what the reason was to remove Element and Node types, so this PR might be uncalled for.
My projects already have "dom" added to the compilerOptions so I needed this anyway, so I figured I might as well submit a PR.

I reckon any project using puppeteer will benefit from adding dom types to the compiler options anyway, and deno doesn't type check remote modules in deno run by default since 1.22. So I don't think there should be any issues in bringing these types back.

Fixes #54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

$eval and $$eval TypeScript return types incorrectly wrap all values in ElementHandle

1 participant