staytuned_teamS
Deno•11mo ago•
12 replies
staytuned_team

Problems with Nested deno.json in Deno Workspaces

Hello ,

I'm encountering an issue in Deno workspaces with nested 
deno.json
 files. As reported in my GitHub issue [https://github.com/StaytunedLLP/open_poc/issues/4], adding 
deno.json
 inside subfolders (like feature folders 
fe_
 and 
sy_
 within workspace packages) leads to red squiggles and broken import navigation in VS Code (using the Deno extension). The code runs correctly, but the editor experience is really suffering.

I'm wondering if anyone can offer guidance on:

* Is this a known limitation or bug in the Deno VS Code extension or Deno itself?
* Is there a recommended workaround or configuration to avoid this issue when using nested 
deno.json
 in workspaces?

I've provided detailed reproduction steps, example folders (
deno-workspace-working
 and 
deno-workspace-not-working
 in the linked issue), and screenshots in the GitHub issue. Any help or direction would be greatly appreciated!

Thanks in advance for your support!
Was this page helpful?