Handoff — 2026-09-16 — the sixth editor, Turbo JS
State
Five files and one comment edited to count six editors; see the history entry of the same date. Uncommitted, on main, on top of the also-uncommitted ACP trace work of 2026-09-16 (see 2026-09-15-acp-commands-mentions.md).
Next steps
- Commit alongside turbo-js's first commit. No tag needed — the editor pins
v0.8.0, which exists. - Two library cycles turbo-js exposed, when wanted: (a)
lsp.Client.DidOpen'slanguageIdshould come from the profile rather than be"go"; (b) pull diagnostics —textDocument/diagnostic, advertised by a server'sdiagnosticProvidercapability — which would let a JavaScript editor run on TypeScript 7's own server from a singlenpm install -g typescript. turbo-js'sinternal/jslang/editor_test.gois a ready-made harness for (b): point its profile at/path/to/node_modules/.bin/tscwith--lsp --stdioand the diagnostics test is the one that fails today.
Watch out for
Registerreplacing a built-in is now exercised by a shipping editor. A change to the built-in JavaScript scanner's name would silently stop turbo-js's override; itsLanguageconstant issyntax.LanguageJavaScripton purpose.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
|