Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📖 add docs about dnt 💗 monorepo #403

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Gaubee
Copy link
Contributor

@Gaubee Gaubee commented Apr 27, 2024

Add documentation describing how to compile Monorepo-style projects with dnt.

@Gaubee Gaubee force-pushed the patch-1 branch 3 times, most recently from 53c5984 to 9354cf0 Compare April 27, 2024 07:45
Add documentation describing how to compile Monorepo-style projects with dnt.
@wKich
Copy link

wKich commented Aug 16, 2024

@Gaubee, thanks for explaining how to build npm packages in Deno monorepo. But according to your example, you are using import_map.npm.json for importMap, so if I also have imports in deno.json it seems there is no simple way to combine both maps together, right?

I don't see version resolving for packages described in import_map.npm.json. Is built package always depends on the latest version, because there is no version specified in the import map? Hm... it is. Which actually really bad behaviour that might break old version packages.

I wonder, why dnt can't resolve imports from a deno workspace configuration without need to adding complexity to a project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants