-
Notifications
You must be signed in to change notification settings - Fork 146
Issues: denoland/vscode_deno
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Symbols are listed twice when Deno is enabled
needs investigation
#1202
opened Oct 31, 2024 by
klaussner
"Cancel Test Run" button in "Test Results" window does not work as expected.
#1201
opened Oct 31, 2024 by
WilcoKruijer
Bug: VSCode LSP doesn't recognize deep types when using
sloppy-imports
#1199
opened Oct 28, 2024 by
Jimdooz
tsconfig prompts don't show up if root dir is a workspace member without a deno.json
#1180
opened Oct 12, 2024 by
nathanwhit
[FR] Seamless Profiling and Performance Checking for Deno in VS Code
#1179
opened Oct 12, 2024 by
beingminimal
Support for --unstable-component as .vue, .svelte, .astro formatter in VSCode
#1178
opened Oct 12, 2024 by
epver
File name differs from already included file name only in casing [deno-ts(1149)]
#1169
opened Sep 26, 2024 by
ericarthurc
High CPU, memory usage and OS crash when JSDoc importing
"/dev/random"
#1158
opened Sep 6, 2024 by
nnmrts
Allow
NO_COLOR
env var to be overridden by deno.env
workspace setting
#1156
opened Sep 3, 2024 by
ArmaanAS
useTabs: true
not respected when formatting via vscode deno extension
#1140
opened Aug 8, 2024 by
scarf005
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.