Workspace-aware path imports
Hi!
My use case: I want to import a package from a Deno workspace. It doesn't work:
- Simply specifying path to the package root or its
- Consequently, Deno isn't aware of package's
I am using the same mental model that works with Cargo: just specify the path, and Cargo will resolve everything.
Cargo understands that this is a crate, and it is a part of a workspace, and Cargo will resolve this crate's dependencies and everything accordingly.
I would really like if it works in Deno the same way.
Or is there a way to achieve the same right now?
My use case: I want to import a package from a Deno workspace. It doesn't work:
- Simply specifying path to the package root or its
deno.jsoncdeno.jsonc doesn't work- Consequently, Deno isn't aware of package's
exportsexports and, more importantly, importsimportsI am using the same mental model that works with Cargo: just specify the path, and Cargo will resolve everything.
Cargo understands that this is a crate, and it is a part of a workspace, and Cargo will resolve this crate's dependencies and everything accordingly.
I would really like if it works in Deno the same way.
Or is there a way to achieve the same right now?
