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!8 Replies
@marvinh. Can you please help us here?
I currently don't have the bandwidth to look into that.
Is this a known limitation or bug in the Deno VS Code extension or Deno itself?If it's in our issue tracker, then it's known. If it's not in our issue tracker, then it's not known. Best way to get help is to file an issue https://github.com/denoland/deno/issues
@dsherret Can you please help us here? because it's regarding deno workspace
can you open an issue with a reproduction?
it would be good to show what the repo looks like in the reproduction because i'm not sure how this looks
what would be best is just an example repo that I can checkout that shows the issue. Otherwise it's hard to follow what the setup looks like
example repo folder path is already there in issue description for same repo
please help https://github.com/StaytunedLLP/open_poc/issues/4
GitHub
Import Navigation Fails in Nested Deno Workspaces · Issue #4 · St...
Red Squiggles & Broken Navigation with Nested deno.json in Workspaces Issue Details Purpose and Value Problem: In Deno workspaces, using nested deno.json files within subfolders (e.g., feature ...
it seems it's a workspace containing a package containing a package? I don't think that's supported
actually, that's a package containing a package containing a package. I think just have a single deno.json at the root and only have one deno.json per part of the tree instead of many nested deno.json packages
ok let me try that way and revert to you. thanks for your support
@dsherret is there any way to export all .ts file from deno workspace member, either from root level of member or any child folder in member directory?
not at the moment. See https://github.com/denoland/deno/issues/26693
GitHub
Deno fails when a package in a monorepo uses a
./* export · Issu...Deno version $ deno --version deno 2.0.4 (stable, release, x86_64-unknown-linux-gnu) v8 12.9.202.13-rusty typescript 5.6.2 To demonstrate the issue I created the following mono-repo $ tree . ├── a ...