packages/web/src/routes/docs/contributors/visual-studio-code/+page.md
This document details how to develop the Visual Studio Code extension locally. If you're interested in how it's packaged and distributed, you can check out the Release VS Code Plugin workflow.
packages/vscode-plugin/src directory. Most changes you'll need to make will be there.packages/vscode-plugin/.vscode if packages/vscode-plugin, not the root of the Harper repository, is open.justfile to see exactly what running the just recipes below does.just setup as the guide recommends to make sure the extension's dependencies are installed.connor4312.esbuild-problem-matchers, so VS Code can understand and run esbuild tasks.harper-ls in packages/vscode-plugin/bin. You can either manually create the directory, compile harper-ls, and put it there or you can run just test-vscode or just package-vscode which will do that for you.Following these steps will open the extension in a new Extension Development Host window, so you can view your changes.
Ctrl+Shift+D.Run Extension, if not chosen already.F5.You may run the following command to run the tests, this is the recommended way.
just test-vscode
Remember: VS Code can only pick up the tasks and launch configurations set in packages/vscode-plugin/.vscode if packages/vscode-plugin, not the root of the Harper repository, is open.
That means you need to manually open VS Code in the vscode-plugin directory yourself.
You may also follow these steps to run the tests through your VS Code installation.
Ctrl+Shift+D.Test Extension, if not chosen already.F5.Package the extension:
just package-vscode
Install the extension:
code --install-extension path/to/created/.vsix