You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Monorepo Support
When package.json is present and references
workspace:*
dependencies, it's still required to manually map paths indeno.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.The text was updated successfully, but these errors were encountered: