Highlight error sources with twinkleplop, update to Solid rc.9

[lxsmnsyc]

• Replace shiki with twinkleplop. Highlighting is synchronous and ships no WebAssembly, so the build drops from 8.1 MB to 3.6 MB.
• Mark the frame's line with the focus directive and the word it points at with err.
• Highlight the whole file, then keep 25 lines on each side of the frame, so a block comment above the window no longer breaks the colours.
• Update every dev dependency, including Solid 2.0.0-rc.9, which needs @solidjs/compiler in place of @dom-expressions/compiler.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​twinkleplop/​tsx@​0.1.5
	@​twinkleplop/​typescript@​0.1.5
	@​twinkleplop/​theme-github@​0.2.2
	@​twinkleplop/​annotation@​0.1.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Low adoption: npm @twinkleplop/annotation Location: Package overview From: package.json → npm/@twinkleplop/annotation@0.1.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/annotation@0.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/core Location: Package overview From: pnpm-lock.yaml → npm/@twinkleplop/theme-github@0.2.2 → npm/@twinkleplop/tsx@0.1.5 → npm/@twinkleplop/annotation@0.1.5 → npm/@twinkleplop/typescript@0.1.5 → npm/@twinkleplop/core@0.2.2 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/core@0.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/css Location: Package overview From: pnpm-lock.yaml → npm/@twinkleplop/tsx@0.1.5 → npm/@twinkleplop/typescript@0.1.5 → npm/@twinkleplop/css@0.1.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/css@0.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/html Location: Package overview From: pnpm-lock.yaml → npm/@twinkleplop/tsx@0.1.5 → npm/@twinkleplop/typescript@0.1.5 → npm/@twinkleplop/html@0.1.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/html@0.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/javascript Location: Package overview From: pnpm-lock.yaml → npm/@twinkleplop/tsx@0.1.5 → npm/@twinkleplop/typescript@0.1.5 → npm/@twinkleplop/javascript@0.1.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/javascript@0.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/theme-github Location: Package overview From: package.json → npm/@twinkleplop/theme-github@0.2.2 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/theme-github@0.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/tsx Location: Package overview From: package.json → npm/@twinkleplop/tsx@0.1.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/tsx@0.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Low adoption: npm @twinkleplop/typescript Location: Package overview From: package.json → npm/@twinkleplop/typescript@0.1.5 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@twinkleplop/typescript@0.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report

[ryansolid]

Rebased this onto main (841fc15) so it can ship in 1.0.0-next.5 — thank you for the highlighter work, @lxsmnsyc. The branch head moved from 5ddbecc to 3f47c8e.

Kept (your four commits, authorship preserved): the shiki → @twinkleplop/* swap, highlight.ts, marker.ts with its unit test (focus/err directive comments, ±25-line window cut after highlighting the whole file), the CodeView.tsx / styles.css changes, the e2e assertions, and .changeset/twinkleplop-highlighting.md.

Dropped: the chore: update dependencies to Solid 2.0.0-rc.9 commit and .changeset/solid-rc-9.md. #21 already moved main to rc.13 (@solidjs/compiler in rolldown.config.js and the fixture, vite-plugin next.46, the development condition via playwright.config.ts, the registry-test hook mock), so that half was superseded and its changeset would have printed a wrong "rc.9" changelog line. The only conflicts were package.json (took main's Solid pins, re-applied the twinkleplop additions and the shiki removal) and pnpm-lock.yaml (regenerated from main's lockfile).

One small commit on top carries the rebase fix-ups: the @twinkleplop/* ranges move to the patches the regenerated lockfile resolved (0.1.5 / theme-github 0.2.2, published Sep 25), and .changeset/rc12-runtime-parity.md now says rc.13, which is what package.json actually pins (rc.12 was never published).

Verification on the rebased branch

• pnpm test: 109 passed (main: 96; +13 from marker.test.ts, which also exercises codeToHtml)
• pnpm test:e2e: 8/8 — captures client errors asserts .twinkleplop, .l.focus, .tok.error, the window bounds and the dropped markers
• pnpm typecheck, pnpm check (publint + attw), pnpm format:check: clean
• pnpm build dist: 7.5 MB → 3.8 MB; error-viewer chunk 1.0 MB → 280 kB; onig.wasm asset gone; pnpm ls shiki empty

— Claude via Cursor