You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will be coupled with #787. If you have only one subdirectory with a deno.json, you can work around this in the meantime by specifying "deno.config": "foo/deno.json" in your workspace settings.
Describe the bug
If I define my
deno.json
file at the root my workspace then I get proper Deno language support but if I put it in a folder then I do not.To Reproduce
deno.json
file in "foo" with some"imports"
defined (e.g. for std lib)main.ts
file in "foo" and import something leveraging the "imports" defined in thedeno.json
fileNote how you'll get an error message from VSCode:
However running
deno run foo/main.ts
works fine (and creates adeno.lock
file too)Expected behavior
The VSCode Deno extension should provide code completion inside the subfolder just as it would if
deno.json
were at the root of the workspace instead.Screenshots
Versions
vscode: 1.82.2 deno: 1.37.0 extension: 3.23.1
The text was updated successfully, but these errors were encountered: