DenoDDeno
Powered by
JolanJ
Denoβ€’5mo agoβ€’
6 replies
Jolan

LSP auto-import in workspaces

What ?


The Deno LSP seems to partially work in a workspace context.
I've made a GitHub repository that can help you reproduce the issue: https://github.com/aburii/hono-backend

Basically you want to have auto imports resolving to your
deno.json
deno.json
's
name
name
property but it struggles to do so. Sometimes it will, sometimes it won't (mostly won't).
-> go to: image 1

I've notficed that the auto-fix feature does not resolve aswell (might be a all-in-one issue).
-> go to: image 2 & 3

Anyone expieriencing the same ? I've noticed some issues on GitHub that are now closed but don't bring any clear solutions.

Which versions am I on ?

Deno :
deno 2.5.4
deno 2.5.4

VSCode plugin :
denoland.vscode-deno 3.46.1
denoland.vscode-deno 3.46.1

TypeScript :
5.9.2
5.9.2
image.png
image.png
image.png
GitHub
GitHub - aburii/hono-backend
Contribute to aburii/hono-backend development by creating an account on GitHub.
GitHub - aburii/hono-backend
Deno banner
DenoJoin
Chat about Deno, a modern runtime for JavaScript and TypeScript.
20,944Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?

Similar Threads

auto import in VSCode/Zed (general LSP support for auto importing)
CCPatriotCCCPatriot / help
16mo ago
Deno LSP doesn't recognize workspaces as imports
BloxsBBloxs / help
2y ago
Deno LSP Issue with import maps?
ZidanZZidan / help
2y ago
Auto Import Not Working
VincentVVincent / help
16mo ago