The Wire · Showcase
vue-tsc fix unblocks rspack plugin type checking
By RepoJournal · Filed · About Vue.js
Copilot patched a vue-tsc crash that was breaking the TypeScript API path used by ts-checker-rspack-plugin.
The vue-tsc crash [1] came from a Symbol that failed to serialize over Node.js IPC once getLanguagePlugins ran lazily after run() returned. The fix [2] swaps that Symbol for an Error, so bundled tooling like ts-checker-rspack-plugin can type-check without blowing up. It is the only code change shipped this period, alongside the router's new docs [3] on encoding paths in navigation. The docs clarify that string paths and object path locations must already be URL-encoded, and add examples for router.push and RouterLink plus migration-guide notes [4]. If you have been hitting "Symbol() could not be cloned" in CI or editor tooling, pull in the fix before your next type-check run.
One email a day. Unsubscribe in one click.
Keep up with Vue.js in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Test vue-tsc against ts-checker-rspack-plugin to confirm the retryToken crash is resolved vuejs/language-tools [immediate]
- → Review the new encoded path navigation docs to ensure your route paths are already URL-encoded vuejs/router [monitor]
References
- [1] fix(tsc): replace symbol `retryToken` with error to allow IPC serialization ↗ vuejs/language-tools
- [2] fix(tsc): replace symbol `retryToken` with error to allow IPC serialization (#6162) vuejs/language-tools
- [3] docs: explain encoded path navigation (#2787) vuejs/router
- [4] docs: explain encoded path navigation ↗ vuejs/router