Clean Integration of a Multi-file Deno Project as a Dependency in another Deno Project
Hey everyone, I’m facing an issue integrating a multi-file Deno project into another Deno project. The challenge is that the files I need to import have their own internal imports, which makes the usual GitHub URL method unfeasible.
I’ve already tried using the dnt approach. It works fine when there aren’t many npm packages involved, but once the dependency graph gets heavier, I start running into odd build errors. My goal is to ensure that everything exported from the project's mod.ts (which just aggregates a bunch of export statements) is fully accessible in the consuming project.
Has anyone successfully tackled this scenario? What is the cleanest and most reliable method to use a multi-file Deno project as a dependency within another project?
Note: I'm using React in the deno sub-projects and my main project has Next.js currently on node, but I'll also be porting this over to deno.
Thanks in advance for your help!
I’ve already tried using the dnt approach. It works fine when there aren’t many npm packages involved, but once the dependency graph gets heavier, I start running into odd build errors. My goal is to ensure that everything exported from the project's mod.ts (which just aggregates a bunch of export statements) is fully accessible in the consuming project.
Has anyone successfully tackled this scenario? What is the cleanest and most reliable method to use a multi-file Deno project as a dependency within another project?
Note: I'm using React in the deno sub-projects and my main project has Next.js currently on node, but I'll also be porting this over to deno.
Thanks in advance for your help!
