Meep
Dependency tree not resolving properly for deno modules in local filesystem.
My issue with workspaces comes when both meep/projects/kms/libs/core and meep/projects/bbnf/libs/parser need to use the packages in the meep/libs/deno folder.
The only way I could see it working without some kind of nested workspaces or allowing workspace folders to be non-nested is if I make a deno.json file for each project but put it in the root meep/ folder which seems like an incorrect place for project files~
10 replies