You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a5fcc2d
Browse filesBrowse the repository at this point in the historyBrowse files
@node-core/doc-kit 2 moved its internals to @doc-kit/core, and removed
the two helpers invalid-type-reference was built on:
`transformTypeToReferenceLink` and `QUERIES.normalizeTypes`.
- duplicate-stability-nodes and validate-links import the same modules
from @doc-kit/core.
- invalid-type-reference keeps its type pattern locally and resolves
each `|` member with doc-kit's `resolveTypeReference`, so it accepts
exactly what the generator can link. Types never reach it with `<>`
in them, so the old generic handling is gone.
- The old resolver accepted anything containing a `.`, which hid HTML
comments and tags being read as `<type>` references. The html branch
now only matches bare `<name>` nodes.
- doc-kit 2 no longer turns `_` into `-` in slugs, matching the site's
rehype-slug and the Node.js API anchors (`#child_process`).
Over Node.js's doc/api with its type-map.json, the rule reports nothing
new: it drops the HTML false positives (7103 -> 283 messages) and now
resolves {object}, {QuotaExceededError}, {WorkerGlobalScope} and
{DedicatedWorkerGlobalScope}. The site's markdown lint stays clean.
Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
Use `@doc-kit/core` instead of `@node-core/doc-kit` 1.x. Heading anchors now follow doc-kit 2's slugs (`child_process` links as `#child_process`), and `invalid-type-reference` no longer treats HTML comments and tags as type references.
0 commit comments