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
I noticed that NPM imports inside deno.json cannot be specified as a peer dependency using @deno/dnt and always end up inside dependencies. When specifying the import using esm.sh/ it works, however.
Replacing the import with the esm.sh/ version correctly transforms blockly as peer dependency while using the npm: version keeps it as direct dependency.
As a workaround one has to keep a separate import map or manually specify dependencies inside package in the build script.
The text was updated successfully, but these errors were encountered:
I'm running into the same problem. For now solving it with a different approach. I overwrite the generated package.json with the unintentional dependencies as dev dependencies.
Hello
I noticed that NPM imports inside
deno.json
cannot be specified as a peer dependency using@deno/dnt
and always end up insidedependencies
. When specifying the import usingesm.sh/
it works, however.Minimal example using Blockly as dependency:
deno.json
:mod.ts
:build_npm.ts
:Replacing the import with the
esm.sh/
version correctly transformsblockly
as peer dependency while using thenpm:
version keeps it as direct dependency.As a workaround one has to keep a separate import map or manually specify dependencies inside
package
in the build script.The text was updated successfully, but these errors were encountered: