WebReflection / WebReflection/linkedom
Typescript type errors
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.1k
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I'm running into loads of type errors from linkedom when using the library in a typescript project.
These type errors appear to all be either missing properties or incorrect implementations of base class methods (due to parameter types or return types not matching).
The errors are too long to send but I will send a few:
node_modules/linkedom/types/dom/parser.d.ts:12:5 - error TS2416: Property 'parseFromString' in type 'DOMParser' is not assignable to the same property in base type 'DOMParser'.
Type '<MIME extends "image/svg+xml" | "text/html" | "text/xml">(markupLanguage: string, mimeType: MIME) => { "text/html": HTMLDocument; "image/svg+xml": SVGDocument; "text/xml": XMLDocument; }[MIME]' is not assignable to type '(string: string, type: DOMParserSupportedType) => Document'.
Type 'HTMLDocument | SVGDocument | XMLDocument' is not assignable to type 'Document'.
Type 'HTMLDocument' is missing the following properties from type 'Document': URL, alinkColor, anchors, applets, and 181 more.
12 parseFromString<MIME extends keyof {
~~~~~~~~~~~~~~~
node_modules/linkedom/types/html/anchor-element.d.ts:4:14 - error TS2420: Class 'import("C:/Users/felis/home/projects/test-linkedom/node_modules/linkedom/types/html/anchor-element").HTMLAnchorElement' incorrectly implements interface 'HTMLAnchorElement'.
Type 'HTMLAnchorElement' is missing the following properties from type 'HTMLAnchorElement': charset, coords, hreflang, name, and 132 more.
4 export class HTMLAnchorElement extends HTMLElement implements globalThis.HTMLAnchorElement {
~~~~~~~~~~~~~~~~~
...
node_modules/linkedom/types/html/document.d.ts:6:9 - error TS2416: Property 'all' in type 'HTMLDocument' is not assignable to the same property in base type 'HTMLDocument'.
Property 'namedItem' is missing in type 'NodeList' but required in type 'HTMLAllCollection'.
6 get all(): NodeList;
~~~
../../../AppData/Roaming/npm/node_modules/typescript/lib/lib.dom.d.ts:5953:5
5953 namedItem(name: string): HTMLCollection | Element | null;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'namedItem' is declared here.
node_modules/linkedom/types/html/document.d.ts:15:9 - error TS2416: Property 'title' in type 'HTMLDocument' is not assignable to the same property in base type 'HTMLDocument'.
Type 'HTMLTitleElement' is not assignable to type 'string'.
15 set title(arg: HTMLTitleElement);
~~~~~
...
Workaround: tsc --skipLibCheck
It'd be great to get the types correct here so --skipLibCheck isn't needed. I would make a PR for this however it seems design decisions would need to be made to fix the types. I'm not sure if the types can be reconciled while still extending / implementing globalThis.DOMParser, globalThis.HTMLElement, /globalThis\.HTML.*Element/, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the errors with TypeScript and inspect the declarations under types/dom/parser.d.ts, types/html/anchor-element.d.ts, and types/html/document.d.ts alongside TypeScript's lib.dom.d.ts. Compare the reported inherited and implemented signatures to determine whether the types can be reconciled with the global DOM interfaces. Done means the reported type errors no longer require tsc --skipLibCheck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100