LSP badly resolves relative imports between cached modules
I don't really understand this, but it looks to me like the LSP / VS Code has started resolving relative imports between cached modules badly.
I'm running under a devcontainer, with the project root in
If I open the (cached) module containing the failing import and hover the import statement I see a popup with the "Resolved Dependency" in the wrong place, outside the cache. Screenshots attached.
I've tried
I'm fairly new to both Deno and VS Code, so please let me know if there is more debug information I can collect, or if there's anything else I should try to resolve the problem or investigate further. Thanks!
I'm running under a devcontainer, with the project root in
/workspace/$DENO_DIR/deno/.cache/deno/workspace/deno/.cache/deno/...If I open the (cached) module containing the failing import and hover the import statement I see a popup with the "Resolved Dependency" in the wrong place, outside the cache. Screenshots attached.
I've tried
deno cache -rI'm fairly new to both Deno and VS Code, so please let me know if there is more debug information I can collect, or if there's anything else I should try to resolve the problem or investigate further. Thanks!
