Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / denoland/vscode_deno issues and pull requests
#873 - Alias & relative imports with importmap: requires prefix
Issue -
State: closed - Opened by Pictor13 over 1 year ago
- 3 comments
Labels: documentation, needs investigation, import maps
#872 - Inconsistent behaviour when using triple-slash directives
Issue -
State: closed - Opened by smitssjors over 1 year ago
- 4 comments
Labels: bug, fresh
#871 - A way to disable deno for JavaScript
Issue -
State: closed - Opened by Mqxx over 1 year ago
- 4 comments
Labels: enhancement, needs investigation, configuration
#860 - Not working, confusing error message with"editor.formatOnSaveMode": "modificationsIfAvailable"
Issue -
State: closed - Opened by rotu over 1 year ago
- 4 comments
Labels: wontfix, needs investigation, configuration, fmt
#859 - vscode_deno consumes over 700MB memory on Windows
Issue -
State: closed - Opened by liigo over 1 year ago
- 1 comment
Labels: needs investigation, windows, perf
#858 - add "registry" Settings option
Pull Request -
State: closed - Opened by marcushultman over 1 year ago
- 5 comments
Labels: configuration
#837 - Cannot import npm specifier modules due to firewall
Issue -
State: closed - Opened by justinmchase almost 2 years ago
- 9 comments
Labels: configuration, high priority, node compat
#834 - deno.enablePaths: pattern support
Issue -
State: open - Opened by mfulton26 almost 2 years ago
- 10 comments
Labels: enhancement, needs investigation, configuration, dx
#834 - deno.enablePaths: pattern support
Issue -
State: open - Opened by mfulton26 almost 2 years ago
- 10 comments
Labels: enhancement, needs investigation, configuration, dx
#824 - Very slow intellisense (tab completion / ctrl+space menu)
Issue -
State: closed - Opened by qgates almost 2 years ago
- 6 comments
Labels: question, needs investigation, windows, dx
#823 - Expose deno.trace.server
Issue -
State: closed - Opened by sigmaSd almost 2 years ago
Labels: enhancement, help wanted
#823 - Expose deno.trace.server
Issue -
State: closed - Opened by sigmaSd almost 2 years ago
Labels: enhancement, help wanted
#793 - BDD Style Tests Not Detected
Issue -
State: open - Opened by jherdman about 2 years ago
- 9 comments
Labels: enhancement, testing
#790 - feat: add default formatter question on initialize
Pull Request -
State: closed - Opened by khaosdoctor about 2 years ago
- 2 comments
#787 - Allow using different deno configs for different dirs
Issue -
State: closed - Opened by kt3k about 2 years ago
- 2 comments
Labels: enhancement, high priority, dx
#782 - feat: include and exclude options for InlayHints
Issue -
State: closed - Opened by thomas3577 about 2 years ago
- 2 comments
Labels: suggestion, dx
#777 - Add setting to hide `Implicitly using latest version` lints
Issue -
State: open - Opened by nikitavoloboev about 2 years ago
- 5 comments
Labels: suggestion, configuration, dx
#776 - feat: support codeLens.testEnvs
Pull Request -
State: closed - Opened by ahuigo about 2 years ago
- 13 comments
#767 - Add `experimental.enableProjectDiagnostics` setting.
Issue -
State: open - Opened by TheCymaera about 2 years ago
- 2 comments
Labels: needs investigation, configuration, maybe fix available
#767 - Add `experimental.enableProjectDiagnostics` setting.
Issue -
State: open - Opened by TheCymaera about 2 years ago
- 2 comments
Labels: needs investigation, configuration, maybe fix available
#708 - debug wasm: Uncaught TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
Issue -
State: open - Opened by ahuigo over 2 years ago
- 11 comments
Labels: bug, needs investigation, debugger
#701 - VSCode should provide indication of config file being used
Issue -
State: closed - Opened by kitsonk over 2 years ago
- 6 comments
Labels: enhancement, good first issue, dx
#674 - "deno.cache" in global settings causes creation of deno-dir even if deno.enable is false
Issue -
State: closed - Opened by qgates over 2 years ago
- 2 comments
Labels: needs investigation, design limitation, maybe fix available
#668 - `deno.enablePaths` conflict with build in typescript language server.
Issue -
State: closed - Opened by nurmohammed840 over 2 years ago
- 14 comments
Labels: bug, windows
#667 - Launching server using command deno failed.
Issue -
State: closed - Opened by AmelloAster almost 3 years ago
- 6 comments
Labels: needs info
#634 - Make sending initial workspace config less fragile
Issue -
State: closed - Opened by kitsonk almost 3 years ago
- 1 comment
Labels: enhancement
#587 - Deno server crashing constantly
Issue -
State: closed - Opened by kyleg55 about 3 years ago
- 14 comments
Labels: needs info, maybe fix available
#515 - Support installation as a Web Extension
Issue -
State: open - Opened by jsejcksn over 3 years ago
- 8 comments
Labels: enhancement, needs investigation
#515 - Support installation as a Web Extension
Issue -
State: open - Opened by jsejcksn over 3 years ago
- 8 comments
Labels: enhancement, needs investigation
#488 - [Feature Request] Support multiple tsconfigs in the same repository
Issue -
State: closed - Opened by guidsdo over 3 years ago
- 8 comments
Labels: high priority, dx
#480 - Language server starts crashing while working on checker.ts in the TypeScript code base
Issue -
State: closed - Opened by dsherret over 3 years ago
- 2 comments
Labels: needs investigation, suggestion, maybe fix available
#466 - Cannot find name 'Deno'
Issue -
State: closed - Opened by jerrygreen over 3 years ago
- 27 comments
Labels: needs investigation
#437 - Plugin incompatible with built-in tsserver `enableProjectDiagnostics`
Issue -
State: open - Opened by Timmmm over 3 years ago
- 23 comments
Labels: enhancement
#437 - Plugin incompatible with built-in tsserver `enableProjectDiagnostics`
Issue -
State: open - Opened by Timmmm over 3 years ago
- 24 comments
Labels: enhancement
#318 - [Canary] DOM is not being included when declared as a lib in tsconfig
Issue -
State: closed - Opened by arocide about 4 years ago
- 10 comments
#318 - [Canary] DOM is not being included when declared as a lib in tsconfig
Issue -
State: closed - Opened by arocide about 4 years ago
- 10 comments
#234 - could not find deno in path, please install deno
Issue -
State: closed - Opened by JSchermers over 4 years ago
- 27 comments
Labels: needs info
#102 - Semicolon added on paste
Issue -
State: closed - Opened by AndreJesusBrito over 4 years ago
- 7 comments
Labels: bug
#101 - Deno fmt even when disabled
Issue -
State: closed - Opened by ShayBox over 4 years ago
- 12 comments
Labels: bug
#100 - Extension causes high cpu load
Issue -
State: closed - Opened by zemse over 4 years ago
- 3 comments
Labels: bug
#99 - Command 'Deno: Restart Deno Language server' resulted in an error
Issue -
State: closed - Opened by alexweininger over 4 years ago
- 1 comment
Labels: bug
#98 - Solution style tsconfig.json causes language server to crash
Issue -
State: closed - Opened by muuvmuuv over 4 years ago
- 1 comment
Labels: enhancement
#97 - @deno-types does not work on first load
Issue -
State: closed - Opened by Ciantic over 4 years ago
- 10 comments
Labels: bug
#96 - Confusing use of the term ‘built-in’?
Issue -
State: closed - Opened by shelby3 over 4 years ago
- 3 comments
Labels: documentation
#95 - Importing from npm packages?
Issue -
State: closed - Opened by bitjson over 4 years ago
- 2 comments
#94 - Extension not compatible with VSCode Version 1.33.1
Issue -
State: closed - Opened by pranjul-sharma over 4 years ago
- 2 comments
#93 - "Deno": Unknown word.
Issue -
State: closed - Opened by justdayan over 4 years ago
- 7 comments
Labels: bug
#92 - Add "enablePatterns" config option
Pull Request -
State: closed - Opened by Flaque over 4 years ago
- 4 comments
#91 - ESLint support
Issue -
State: closed - Opened by jsejcksn over 4 years ago
- 4 comments
Labels: enhancement
#90 - An import path cannot end with a '.ts' extension.
Issue -
State: closed - Opened by JeongHoJeong over 4 years ago
- 8 comments
Labels: bug
#89 - TypeScript language service dies when denoland.Deno extension enabled in a React/TypeScript app
Issue -
State: closed - Opened by zeljkoantich over 4 years ago
- 9 comments
Labels: bug
#88 - Deno logo for vscode ext has poor quality
Issue -
State: closed - Opened by gokulkrishh over 4 years ago
- 1 comment
#87 - Disable extension for a subdirectory
Issue -
State: closed - Opened by ghost over 4 years ago
- 3 comments
Labels: enhancement
#86 - Cannot find module
Issue -
State: closed - Opened by newtack over 4 years ago
- 14 comments
Labels: bug
#85 - (Unsure of source of bug) TS Server fatal error: Cannot read property 'get' of undefined
Issue -
State: closed - Opened by AbhinavRobinson over 4 years ago
- 2 comments
Labels: bug
#84 - revert changes to get it working again
Pull Request -
State: closed - Opened by ry over 4 years ago
- 1 comment
#83 - Plugin doesn't work at all
Issue -
State: closed - Opened by tahmid-hasan over 4 years ago
- 5 comments
#82 - WSL2 Failed to load node_modules for typescript support.
Issue -
State: closed - Opened by fenilli over 4 years ago
- 1 comment
#81 - Plugin does not respect user tab settings
Issue -
State: closed - Opened by xXACCEXx over 4 years ago
- 6 comments
Labels: bug
#80 - [pre version 2] Extension doesn't seem to do anything
Issue -
State: closed - Opened by brundonsmith over 4 years ago
- 48 comments
#79 - Publish releases
Issue -
State: closed - Opened by kbarbounakis over 4 years ago
- 2 comments
#78 - [Discussion] Possible solution to fix delays and versioning confusion: Merge `typescript-deno-plugin` into `vscode_deno`?
Issue -
State: closed - Opened by David-Else over 4 years ago
- 7 comments
#77 - Fix broken installation of TS definition files for `Deno`.
Pull Request -
State: closed - Opened by denisbrodbeck over 4 years ago
- 3 comments
#76 - Fix incorrect configuration string in README
Pull Request -
State: closed - Opened by NurMarvin over 4 years ago
#75 - Set root folder for plugin
Issue -
State: closed - Opened by parliament718 over 4 years ago
- 5 comments
Labels: enhancement
#74 - Why vs code doesn't show types for Deno
Issue -
State: closed - Opened by niyarlatotep over 4 years ago
- 19 comments
#73 - can't resolve wsl paths on windows10
Issue -
State: closed - Opened by alf-ytakada over 4 years ago
- 2 comments
#72 - Warning prompt in VS Code
Issue -
State: closed - Opened by pedropaulosuzuki over 4 years ago
- 1 comment
Labels: bug
#71 - VScode JS IntelliSense
Issue -
State: closed - Opened by evilsquirrel404 over 4 years ago
- 5 comments
#70 - Does anyone think it's better to set the default value of deno.enable to false
Issue -
State: closed - Opened by lovefengruoqing over 4 years ago
- 4 comments
#69 - Extension is linting JS files like TS even when deno.enable is false
Issue -
State: closed - Opened by dd-pardal over 4 years ago
- 10 comments
Labels: bug
#68 - support deno-types
Pull Request -
State: closed - Opened by justjavac over 4 years ago
#67 - debugger Deno.openSync or Deno.open, Uncaught NotFound
Issue -
State: closed - Opened by chenguzhen87 over 4 years ago
- 2 comments
Labels: bug
#66 - cannot find name 'Deno'
Issue -
State: closed - Opened by itajaja over 4 years ago
- 66 comments
#65 - Files are not unconditionally treated as modules
Issue -
State: closed - Opened by chenguzhen87 over 4 years ago
- 5 comments
Labels: bug
#64 - update releases
Pull Request -
State: closed - Opened by justjavac over 4 years ago
#63 - fix extension's name and publisher
Pull Request -
State: closed - Opened by justjavac over 4 years ago
#62 - Installed Deno support for VSCode, but it did not work
Issue -
State: closed - Opened by chenguzhen87 over 4 years ago
- 15 comments
#61 - Cannot find module 'react-redux'. or any js module
Issue -
State: closed - Opened by mzaien over 4 years ago
- 2 comments
#60 - Can not disable ts type check with vscode settings in node.js project
Issue -
State: closed - Opened by yoyo837 over 4 years ago
- 9 comments
Labels: bug
#59 - auto-publish with github actions
Issue -
State: closed - Opened by ry over 4 years ago
- 2 comments
#58 - Auto imports strictly uses .ts extension even on .tsx files
Issue -
State: closed - Opened by ibrahimduran over 4 years ago
- 3 comments
Labels: bug
#57 - Conflict with Prettier extension
Issue -
State: closed - Opened by rjkz808 over 4 years ago
- 10 comments
Labels: bug
#56 - Option to enable single quotes
Issue -
State: closed - Opened by zemse over 4 years ago
- 3 comments
#55 - rewrite deno finder
Pull Request -
State: closed - Opened by justjavac over 4 years ago
#54 - Option for deno plugin to be enabled in only some directories.
Issue -
State: closed - Opened by dustinroepsch over 4 years ago
- 2 comments
#53 - Updated icon
Pull Request -
State: closed - Opened by Kirlovon over 4 years ago
#52 - Type defs for `Deno` namespace are not found
Issue -
State: closed - Opened by colinknebl over 4 years ago
- 5 comments
#51 - TS prompt error when setting importmap to import package
Issue -
State: closed - Opened by FE-Mars over 4 years ago
- 3 comments
#50 - Feature request - disable Deno extension in Node.js projects
Issue -
State: closed - Opened by rjkz808 over 4 years ago
- 9 comments
Labels: enhancement
#49 - Top-level 'await' is not recognized by extension
Issue -
State: closed - Opened by rjkz808 over 4 years ago
- 5 comments
Labels: bug
#48 - Installed VSCode plugin but still not able to catch deno syntax
Issue -
State: closed - Opened by zemse over 4 years ago
- 22 comments
#47 - Configure deno executable path
Issue -
State: closed - Opened by orzFly almost 5 years ago
- 3 comments
Labels: enhancement
#46 - Squiggly lines
Issue -
State: closed - Opened by ATakaSKY almost 5 years ago
- 10 comments
Labels: bug
#45 - [DOC] change "install" to "installing"
Pull Request -
State: closed - Opened by msal4 almost 5 years ago
#44 - 'TSServer exited with code: 3221225477' since new VSCode version
Issue -
State: closed - Opened by omirobarcelo almost 5 years ago
- 2 comments
#43 - fix auto import
Pull Request -
State: closed - Opened by justjavac almost 5 years ago
#42 - Property 'values' does not exist on type 'ObjectConstructor'
Issue -
State: closed - Opened by makoven almost 5 years ago
- 1 comment
#41 - Using any PIKA.DEV package causes TypeScript language service to die. TS Server fatal error: Maximum call stack size exceeded
Issue -
State: closed - Opened by IgorSzymanski almost 5 years ago
- 2 comments
#40 - Unclear how to indicate tsconfig to plugin
Issue -
State: closed - Opened by Ragzouken almost 5 years ago
- 5 comments