Meep
Meep
DDeno
Created by Meep on 9/27/2024 in #help
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
DDeno
Created by Meep on 9/27/2024 in #help
Dependency tree not resolving properly for deno modules in local filesystem.
Thanks for the reply to provide more info: The issue is workspaces seem to require a nested folder structure. Here is an example of my folder structure if that helps:
- /meep
- projects
- kms
- apps
- client*
- libs
- core*
- bbnf
- libs
- parser*
- libs
- deno
- iter*
- guards*
- types*
- ...etc
- /meep
- projects
- kms
- apps
- client*
- libs
- core*
- bbnf
- libs
- parser*
- libs
- deno
- iter*
- guards*
- types*
- ...etc
10 replies
DDeno
Created by Meep on 9/27/2024 in #help
Dependency tree not resolving properly for deno modules in local filesystem.
I guess I should ask then; how is one expected to manage a tree of local dependencies when developing an app in Deno?
10 replies
DDeno
Created by Meep on 9/27/2024 in #help
Dependency tree not resolving properly for deno modules in local filesystem.
So... Wait maybe I'm misunderstanding; Doesn't that mean Deno itself can't support nested dependencies for its own native type of packages? If that's true I'm not sure how to work around this tbh ..
10 replies
DDeno
Created by Meep on 9/27/2024 in #help
Dependency tree not resolving properly for deno modules in local filesystem.
As a note; I've also tried workspaces but they don't work because the utility packages aren't nested sadly
10 replies