diff options
| author |  sommerfeld <sommerfeld@sommerfeld.dev> | 2026-05-13 13:43:40 +0100 |
|---|---|---|
| committer | sommerfeld <sommerfeld@sommerfeld.dev> | 2026-05-13 13:43:40 +0100 |
| commit | ab8ee06cbfce42f94e07a0a694701a4df9201815 (patch) | |
| tree | cf62051aa2539a939e196047a8ab634b0ff693a6 /meta | |
| parent | 7771ced1411c3140f5ca17bfe282dc23a949c4a6 (diff) | |
| download | dotfiles-ab8ee06cbfce42f94e07a0a694701a4df9201815.tar.gz dotfiles-ab8ee06cbfce42f94e07a0a694701a4df9201815.tar.bz2 dotfiles-ab8ee06cbfce42f94e07a0a694701a4df9201815.zip | |
feat(nvim): pin copilot to Node 24 to dodge LSP/Node 26 incompat
copilot-language-server emits 'HTTP 200 response does not appear to
originate from GitHub' under Node 26 (the current Arch nodejs). Upstream
tracking:
https://github.com/zbirenbaum/copilot.lua/issues/695
https://github.com/github/copilot.vim/issues/282
https://github.com/github/copilot-language-server-release/issues/45
Workaround universally confirmed in those threads is to run the
language-server under Node 24. Rather than downgrade system nodejs (used
by lots of other tooling) install a private Node 24 under
~/.local/share/copilot-node/ via a chezmoi run_onchange script that
verifies the official sha256, and point copilot.lua at it via
copilot_node_command. Drop in once, bump NODE_VERSION when the upstream
incompatibility is resolved.
Diffstat (limited to 'meta')
0 files changed, 0 insertions, 0 deletions