Open taras opened 9 months ago
@taras Does the workaround in that issue work?
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 error