Skip to content

docs: fix DOM type definitions link - #3642

Open
Sean (seanxuu) wants to merge 3 commits into
microsoft:v2from
seanxuu:docs/issue-64118-dom-types-link
Open

docs: fix DOM type definitions link#3642
Sean (seanxuu) wants to merge 3 commits into
microsoft:v2from
seanxuu:docs/issue-64118-dom-types-link

Conversation

@seanxuu

Copy link
Copy Markdown

What changed

  • Update the DOM Manipulation tutorial to link to the current DOM type-definition baseline.

Why

The previous link pointed to microsoft/TypeScript/src/lib/dom.generated.d.ts, which was removed in the TypeScript 7 repository layout. The replacement points to the maintained TypeScript-DOM-lib-generator baseline with the same generated DOM definitions.

Validation

  • git diff HEAD^ HEAD --check
  • Confirmed the replacement URL returns HTTP 200.

References microsoft/TypeScript#64118

@seanxuu
Sean (seanxuu) marked this pull request as ready for review September 3, 2026 07:04
@jakebailey

Copy link
Copy Markdown
Member

You should just do what #3640 did

TypeScript is a typed superset of JavaScript, and it ships type definitions for the DOM API. These definitions are readily available in any default TypeScript project. Of the 20,000+ lines of definitions in _lib.dom.d.ts_, one stands out among the rest: `HTMLElement`. This type is the backbone for DOM manipulation with TypeScript.

> You can explore the source code for the [DOM type definitions](https://github.com/microsoft/TypeScript/blob/main/src/lib/dom.generated.d.ts)
> You can explore the source code for the [DOM type definitions](https://github.com/microsoft/TypeScript/tree/main/tsc/internal/bundled/libs)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You still should point it at the DOM file

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.

2 participants