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

Monorepos, NPM Workspace compatibility / DX #28157

Open
pixeleet opened this issue Feb 17, 2025 · 0 comments
Open

Monorepos, NPM Workspace compatibility / DX #28157

pixeleet opened this issue Feb 17, 2025 · 0 comments

Comments

@pixeleet
Copy link

Monorepo Support

When package.json is present and references workspace:* dependencies, it's still required to manually map paths in deno.json to enable resolution correctly.

Npm Workspaces

It's required to set separate deno workspaces for each and even than the import map needs to be set by hand otherwise specifier resolutions fail even with unstable: ["sloppy-imports", "byonm"]

These seem to be hard breaking issues when trying to integrate Deno into an existing npm monorepo.

About twice a year I try getting @Effect-TS/effect to work with Deno natively by implementing @effect/platform-deno and every time I find that there is a piece still missing for dropping in a piece of deno code into an npm workspace/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

No branches or pull requests

1 participant