fix(js): fix JSR doc-gen for libraries; exclude web-component packages

[kixelated]

Where we are

The deno-based release (run 27509033095) published 5 libraries to JSR: token, json, loc, msf, hang. It then exposed two more server-side issues (invisible to deno publish --dry-run, but reproducible with deno doc):

Issues fixed

1. Doc-gen can't resolve .ts extensions or bare . in the published .d.ts.
JSR generates the API docs by resolving the .d.ts import graph. The dist ships .js/.d.ts (no .ts), so:

• net's export * as Connection from "./connection/index.ts" → Failed resolving './connection/index.ts'
• signals' dom.ts import ... from "." → Failed resolving './/'

Fix: normalize the emitted .d.ts in package.ts - strip .ts extensions and rewrite bare "." → "./index". Only declarations are touched; the .js keeps its specifiers for npm consumers. (The successful libs already used extensionless imports, which is why they worked.)

2. Web components fundamentally can't publish to JSR.
watch/publish/boy fail with modifying global types is not allowed - every custom element augments HTMLElementTagNameMap, and JSR prohibits global type modification outright (--allow-slow-types only silenced the warning). This isn't fixable without dropping the custom-element typing, so these three opt out with "jsr": false. publishJsr now honors that (still defaults on for everything else with a release script).

Validation

All 7 libraries pass deno doc locally - the exact doc generation deno publish runs - across every entrypoint in their generated jsr.json:

net: OK   signals: OK   json: OK   msf: OK   hang: OK   loc: OK   token: OK

The 3 web-component packages no longer generate a jsr.json. Biome clean.

After merge, the release should skip the 5 already-published libs, publish net + signals, and skip the 3 web components → green, with all 7 libraries on JSR.

Note on why this took several rounds

deno publish --dry-run validates packaging and slow types, but license validation and documentation generation only happen server-side at publish, so each surfaced only on a real run. deno doc reproduces the doc-gen step locally and is now part of how these were verified.

(Written by Claude)

🤖 Generated with Claude Code

Also (folded in from #1734)

The Check workflow was failing on a pre-existing docs dead link from #1732 (http://localhost:4443/certificate.sha256 in setup/windows.md). Generalized the VitePress ignoreDeadLinks localhost exemption to a regex so dev-example URLs do not break the doc build. Folded here so this PR is green on its own; #1734 closed as superseded.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 70ef9be2-6d2c-4b46-b948-8a097e7ccbea

📥 Commits

Reviewing files that changed from the base of the PR and between a4a7082 and 08e3ea9.

📒 Files selected for processing (1)

• doc/.vitepress/config.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• doc/.vitepress/config.ts

---

Walkthrough

The PR introduces a "jsr": false opt-out field to three package manifests (js/moq-boy, js/publish, js/watch). The JSR publish gating logic in release.ts switches from checking for a release script to checking pkg.jsr !== false. In package.ts, the gating condition is updated to require both a release script and pkg.jsr !== false, and the pkg.jsr field is explicitly cleared before writing dist/package.json. A new rewriteDtsImports() helper is added that scans dist/**/*.d.ts and rewrites import specifiers by removing .ts suffixes and normalizing bare "." imports to "./index"; this helper is called before JSR config generation steps. Additionally, the VitePress configuration is updated to ignore all localhost URLs with optional port and path instead of just the hardcoded port 5173.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly reflects the main changes: fixing JSR doc-gen for libraries and excluding web-component packages from JSR publishing.
Description check	✅ Passed	The description comprehensively explains the issues fixed, solutions implemented, and validation performed, directly corresponding to the changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/jsr-libs-and-exclude-webcomponents

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@js/common/release.ts`:
- Around line 8-11: The JSR gating logic in release.ts checks only `pkg.jsr !==
false` to determine whether to publish to JSR, but package.ts requires both a
release script AND `pkg.jsr !== false` before generating jsr.json. This mismatch
causes failures when a package lacks a release script but has no explicit `jsr:
false` setting. To align the gating logic across both files, remove the release
script requirement from the jsr.json generation condition in package.ts so that
jsr.json is generated whenever `pkg.jsr !== false`, regardless of whether a
release script exists. This ensures the publishJsr constant in release.ts will
only attempt JSR publishing when the necessary jsr.json file has been generated.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5a1b428d-b26c-4493-99f4-5fa6b209b471

📥 Commits

Reviewing files that changed from the base of the PR and between 39c1ef7 and 3f11321.

📒 Files selected for processing (5)

• js/common/package.ts
• js/common/release.ts
• js/moq-boy/package.json
• js/publish/package.json
• js/watch/package.json

[coderabbitai]

🧹 Nitpick comments (1)

doc/.vitepress/config.ts (1)

264-266: ⚡ Quick win

Expand boundary check to handle query parameters and hash fragments.

The regex won't match localhost URLs with query parameters or hash fragments immediately after the port (e.g., http://localhost:5173?foo=bar or http://localhost:5173#section). While uncommon in documentation, these are valid URLs.

Changing (\/|$) to (\/|\?|#|$) would match all valid localhost URLs while still preventing false positives like http://localhost.example.com.

♻️ Suggested fix for more robust matching

-	/^https?:\/\/localhost(:\d+)?(\/|$)/,
+	/^https?:\/\/localhost(:\d+)?(\/|\?|#|$)/,

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@doc/.vitepress/config.ts` around lines 264 - 266, The regex pattern for
matching localhost URLs in the development examples check currently uses (\/|$)
which only matches a forward slash or end of string, but it doesn't account for
query parameters or hash fragments. Modify the regex pattern by changing (\/|$)
to (\/|\?|#|$) to match localhost URLs that may have query parameters (indicated
by ?) or hash fragments (indicated by #) immediately after the port, while still
maintaining the ability to prevent false positives like
http://localhost.example.com.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@doc/.vitepress/config.ts`:
- Around line 264-266: The regex pattern for matching localhost URLs in the
development examples check currently uses (\/|$) which only matches a forward
slash or end of string, but it doesn't account for query parameters or hash
fragments. Modify the regex pattern by changing (\/|$) to (\/|\?|#|$) to match
localhost URLs that may have query parameters (indicated by ?) or hash fragments
(indicated by #) immediately after the port, while still maintaining the ability
to prevent false positives like http://localhost.example.com.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bce50165-3b66-4220-9df3-453a8b615c18

📥 Commits

Reviewing files that changed from the base of the PR and between 3f11321 and a4a7082.

📒 Files selected for processing (2)

• doc/.vitepress/config.ts
• js/common/release.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• js/common/release.ts