Internally there's a command called pack:dev that does bundling, compilation and installation, why can't we document this command instead? (We can rename it) I found that command very easy

We can, I just assumed people would just run the app with the debug, as I do.

Ok. Sorry if I'm being so dumb, but unfortunately I struggle to understand the flow.

So I open this repository with VSCode, then I click F5, open another project that uses the extension, and when I modify this source the other project will use the new compiled code?

Second thought: the contribution guide assumes that a person uses VSCode, but I use other editors, there's no F5 😅

No problem, I'll try to explain this better.

First, the contribution guide assumes that you're using VS Code to develop the extension because it's the easiest way to debug it. We can definitely improve the guide to include instructions for user who don't use VS Code as their main editor, though.

When you open this repo with VS Code and press F5, VS Code will spawn a separate VS Code instance meant only for debugging. This separate instance does two things:

1. It starts with all extensions disabled
2. It loads and enables the Biome extension being debugged (the watcher builds it in out/)

You can then use this separate instance to load any other project to test the behavior of the Biome extension on a real project.

Hope this clears it.

That's way better, thank you!

Will be overhauled as part of v3.