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
npm packages are supported: You can depend on npm packages by either specifying them in the dependencies of your package.json, or by referencing them in code using npm: specifiers such as import { cloneDeep } from "npm:lodash@4";.
It sounds like JSR lets you do import * as esbuild from 'npm:esbuild@0.20.1.
A minor edge case, but this won't work on Deno Deploy because there is no writable file system. The Deno WASM package works on Deploy but npm:esbuild-wasm doesn't (some Node child processes API isn't compatibility). I guess a JSR package for Deno Deploy is rather niche.
I did look into this further and it'd require the denoflate package being published to JSR first as that's a dependency on the deno side.
JSR is a new package registry.
It would be useful to have the Node and Deno packages (and WASM variants) published there if possible.
Deno in particular does not allow JSR packages to import non-JSR dependencies:
The text was updated successfully, but these errors were encountered: