Skip to content

Republish LSP server before F5 dev-mode launches#45

Open
clrudolphi wants to merge 1 commit into
masterfrom
fix/vscode-f5-stale-server-44
Open

Republish LSP server before F5 dev-mode launches#45
clrudolphi wants to merge 1 commit into
masterfrom
fix/vscode-f5-stale-server-44

Conversation

@clrudolphi

Copy link
Copy Markdown
Collaborator

Summary

  • F5 (Extension Development Host) previously reused whatever server binary was last manually published to bin/Release/net10.0/win-x64/publish/, silently masking source changes and causing phantom "regressions" (see VS Code dev host (F5) can silently run a stale published LSP server #44).
  • Adds scripts/dev-publish-server.mjs, a freshness-check script that republishes the win-x64 server only when source under src/LSP is newer than the last dev publish.
  • Wires it into .vscode/tasks.json as a Run Extension: prelaunch compound task (npm: build:server:dev then npm: compile) and sets it as the preLaunchTask in .vscode/launch.json.

Test plan

  • Ran node scripts/dev-publish-server.mjs with no prior publish — republished successfully.
  • Ran again with no source changes — skipped republish ("up to date").
  • Touched Hosting/Program.cs — script detected staleness and republished; subsequent run skipped again.

Fixes #44

🤖 Generated with Claude Code

F5 previously reused whatever was last manually published to
bin/Release/.../publish, silently masking source changes. Add a
prelaunch task that republishes the win-x64 server only when source
under src/LSP is newer than the last dev publish, keeping the common
no-change case fast.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

VS Code dev host (F5) can silently run a stale published LSP server

1 participant