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
VSCode Deno plugin does not read deno.json when used in multi-root workspace configuration. www/deno.json has imports path for Effection in other dependencies which Deno LSP does not know how to resolve which causes the following error
The text was updated successfully, but these errors were encountered:
No, because it's not the same issue. Our issue isn't that deno.json is in a folder. The problem is that it only reads the deno.json of the root workspace. The workaround in #894 is to make www root, which automatically reads the deno.json with imports relying on the fact that the core doesn't have any imports.
VSCode Deno plugin does not read
deno.json
when used in multi-root workspace configuration.www/deno.json
has imports path for Effection in other dependencies which Deno LSP does not know how to resolve which causes the following errorThe text was updated successfully, but these errors were encountered: