turbo-editors/turbo-core · 2026-09-16-sixth-editor.md

⑂ 28d59854361aeda8541d853093e732126f3d7bff

2026-09-16-sixth-editor.md · 14 lines · 1.2 KBmarkdown    Blame HistoryRaw
   1# Handoff — 2026-09-16 — the sixth editor, Turbo JS
5Five 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`).
7## Next steps
91. Commit alongside turbo-js's first commit. No tag needed — the editor pins `v0.8.0`, which exists.
102. Two library cycles turbo-js exposed, when wanted: (a) `lsp.Client.DidOpen`'s `languageId` should come from the profile rather than be `"go"`; (b) pull diagnostics — `textDocument/diagnostic`, advertised by a server's `diagnosticProvider` capability — which would let a JavaScript editor run on TypeScript 7's own server from a single `npm install -g typescript`. turbo-js's `internal/jslang/editor_test.go` is a ready-made harness for (b): point its profile at `/path/to/node_modules/.bin/tsc` with `--lsp --stdio` and the diagnostics test is the one that fails today.
12## Watch out for
14- `Register` replacing 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; its `Language` constant is `syntax.LanguageJavaScript` on purpose.

🛟 Updated. 28d5985 k33g 20h ago	1	# Handoff — 2026-09-16 — the sixth editor, Turbo JS
	2
	3	## State
	4
	5	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`).
	6
	7	## Next steps
	8
	9	1. Commit alongside turbo-js's first commit. No tag needed — the editor pins `v0.8.0`, which exists.
	10	2. Two library cycles turbo-js exposed, when wanted: (a) `lsp.Client.DidOpen`'s `languageId` should come from the profile rather than be `"go"`; (b) pull diagnostics — `textDocument/diagnostic`, advertised by a server's `diagnosticProvider` capability — which would let a JavaScript editor run on TypeScript 7's own server from a single `npm install -g typescript`. turbo-js's `internal/jslang/editor_test.go` is a ready-made harness for (b): point its profile at `/path/to/node_modules/.bin/tsc` with `--lsp --stdio` and the diagnostics test is the one that fails today.
	11
	12	## Watch out for
	13
	14	- `Register` replacing 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; its `Language` constant is `syntax.LanguageJavaScript` on purpose.