vscode_deno
vscode_deno copied to clipboard
Visual Studio Code plugin for Deno
The setting "deno.path" doesn't seem to resolve environment variables. In my settings.json I want to use an environment variable to resolve to deno. Basically what I would like it to...
**Is your feature request related to a problem? Please describe.** VS Code has the embedded JavaScript Debug Terminal for debugging Node.js applications. It's extremely handy, as you don't need to...
Makes the LSP setting added in https://github.com/denoland/deno/pull/19317 configurable in the VS Code extension
This is a proposed solution to #789. fixes #789
For https://github.com/denoland/vscode_deno/issues/661 This new new option `codeLens.testEnvs` is used to custom environment variables for **deno test**
I would like to see IntelliSense autocompletion for imports from valid registries when those registries have been mapped to arbitrary specifiers using an import map. I'm aware that this issue...
It'd be great to have this extension on the OpenVSX marketplace, to be directly installable from VSCode-compatible editors like [Theia](https://github.com/eclipse-theia/theia) or from VSCode clones like [VSCodium](https://github.com/VSCodium/vscodium), since the Visual Studio...
I like Deno for its capability to replace NodeJS in the long run. But what I like even more on it is the fact that it can do so much...
This might be a duplicate. I'll investigate this later, but logging for now. Maybe I messed something up with my vscode while testing some stuff. **Describe the bug** I was...
**Is your feature request related to a problem? Please describe.** It frustrates me that I can't open one vscode instance for all the projects in my repository. Example of what...