You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current CONTRIBUTING.md document doesn't explain how a contributor can bundle the VSCode extension, and it doesn't explain how to launch VSCode with the bundled extension.
Steps to reproduce
Open the document CONTRIBUTING.md
Check the Development header
It mentions a watch mode for debugging, but it's unclear how it works. I pressed in F5, but it didn't do anything
Expected behavior
I would expect more information for people who aren't accustomed to the developments of the project
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
No response
The text was updated successfully, but these errors were encountered:
AFAIK, the F5 shortcut is VS Code's default to start the debugger, so it should work out of the box. Could you try running the Debug: Start Debugging command from the command palette and see if this works?
Sorry, looking at this flow for the first time and I'm having a hard time. Consider that my experience is very basic and there might be a lot of steps that I'm missing. Does it open two instances of VSCode?
Extension version
main
Biome version
main
Operating system
Description
The current
CONTRIBUTING.md
document doesn't explain how a contributor can bundle the VSCode extension, and it doesn't explain how to launch VSCode with the bundled extension.Steps to reproduce
CONTRIBUTING.md
Development
headerF5
, but it didn't do anythingExpected behavior
I would expect more information for people who aren't accustomed to the developments of the project
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
No response
The text was updated successfully, but these errors were encountered: