Libing Chen

Yes, I think it's better to move it to jbang.dev repo, and all editors can use this schema file from http://jbang.dev/schema.json for code completion.

@maxandersen could you make a review for https://github.com/jbangdev/jbang-idea/blob/main/src/main/resources/jbang-catalog-schema.json then we can move the schema to main repo and submit a PR to https://github.com/SchemaStore/schemastore

How about `jbang template list --catalogs` to list templates from local catalogs? * built-in templates by `jbang template list` * user specified templates by `jbang template list --catalogs` I can...

Which one is better to you? Input or Dropbox? Almost most developers don't like to input because it's easy to make mistake when template name is some long, for example...

I will use JList with input support, and developers can input the template template too. :)

Could you try this version? [vitest-jetbrains-plugin-0.6.2.zip](https://github.com/linux-china/vitest-jetbrains-plugin/files/9377699/vitest-jetbrains-plugin-0.6.2.zip)

I have no dev environment WSL. Please use following version and I use npm path from configuration now. [vitest-jetbrains-plugin-0.6.2.zip](https://github.com/linux-china/vitest-jetbrains-plugin/files/9379464/vitest-jetbrains-plugin-0.6.2.zip)

the correct command should be "\home\saber.nvm\versions\node\v16.14.0\bin\npm.cmd" on WSL?

> or maybe just cut "\wsl${DISTRO_NAME}" out, and it will work @XiaNi @HalfLife7 I build a new version with this way, and anybody can try it? [vitest-jetbrains-plugin-0.6.5.zip](https://github.com/linux-china/vitest-jetbrains-plugin/files/9607340/vitest-jetbrains-plugin-0.6.5.zip)

Yes, I know this problem, and debugging needs more works :) Now you can debug test by https://github.com/linux-china/vitest-jetbrains-plugin#how-to-debug-vitest-tests I will take a look and use run configuration to run Vitest...