GitShow/denoland/vscode_deno
denoland

vscode_deno

Visual Studio Code plugin for Deno

by denoland
Star on GitHubForkWebsitenpm

TypeScript

1.5k stars164 forks69 contributorsActive · 12h agoSince 2020MIT

Meet the team

See all 69 on GitHub →
nayeemrmn
nayeemrmn130 contributions
justjavac
justjavac112 contributions
kitsonk
kitsonk82 contributions
lucacasonato
lucacasonato41 contributions
dsherret
dsherret29 contributions
axetroy
axetroy17 contributions
bartlomieju
bartlomieju16 contributions
ry
ry12 contributions

Recent PRs & issues

Active · Last activity 12h ago
See all on GitHub →
bartlomieju
fix: register $ref'd config sub-schemas so VS Code trusts themOpenPR

Opening in VS Code shows a persistent warning that the lint schema is loaded from an untrusted location: Unable to load schema from 'https://raw.githubusercontent.com/denoland/deno/main/cli/schemas/lint-rules.v1.json': Location ... is untrusted. The schema is registered here from a remote URL, and its lint section resolves through relative s to sibling and files. VS Code's JSON language service ( in ) only trusts schema URLs that are explicitly registered: an exact-URL match against associations, the setting, or . A schema reached only transitively through a , even on the same host, is treated as an untrusted download and blocked. That's why the top-level loads fine but its targets do not, and the subsection silently loses schema validation. This registers those two sibling schema URLs as associations so matches them and the download is allowed. is empty because these are sub-schemas (a single rule name / tag value), not whole-file schemas, so they should never validate a file on their own; the empty array still registers the association purely for the trust check ( passes VS Code's contribution validation). Only and need this, as they are the only cross-file targets in . Closes denoland/deno#35691

bartlomieju · 12h ago
johngeorgewright
Cannot exclude no-slow-types linting rulesOpenIssue

Cannot exclude linting rules While I understand the concept behind this rule, and that it is a good idea to use it when developing new projects to be published to JSR, we don't really want it when trying to convert old projects on to deno. Especially ones that rely on typescript features that would go against the slow-type concept. To Reproduce Create the following file structure: src/ foo.ts deno.json mod.ts Expected behavior No warnings displayed in vscode Screenshots Versions** vscode: 1.124.2 deno: 2.9.0 extension: 3.52.0

johngeorgewright · 1d ago
drewteachout
BDD Tests Not DetectedOpenIssue

Describe the bug Nested describes are not detected in VSCode To Reproduce 1. Create a deno workspace project 2. Create a test file and use the BDD style 3. Nest a describe within a describe 4. Note the lack of green running arrows Expected behavior I expect the nested describe and it blocks to have green arrows so I can run the tests individually. Screenshots Nested Un-nested Versions** vscode: 1.122.1 deno: 2.8.3 extension: 3.52.0

drewteachout · 1w ago

Recent fixes

View closed PRs →
scarf005
Unable to load schema error on `deno.json`ClosedIssue

Describe the bug !image To Reproduce 1. open vscode. 2. open . 3. get following error: Expected behavior Schema is correctly loaded. seems to be vscode issue as the json can be fetched without issue. Versions vscode: 1.93.1 deno: deno 2.0.0-rc.4+4b02210 (canary, release, x86_64-unknown-linux-gnu) extension: 3.40.0

scarf005 · 1w ago
Structured data for AI agents

Repository: denoland/vscode_deno. Description: Visual Studio Code plugin for Deno Stars: 1549, Forks: 164. Primary language: TypeScript. License: MIT. Homepage: https://marketplace.visualstudio.com/items?itemName=denoland.vscode-deno Open PRs: 9, open issues: 116. Last activity: 12h ago. Top contributors: nayeemrmn, justjavac, kitsonk, lucacasonato, dsherret, axetroy, bartlomieju, ry, CGQAQ, dependabot[bot] and others.

·@ofershap

Replace github.com with gitshow.dev