Post

I guess technically is a JSR issue, but I feel really misled by deno's "full npm compatibility" after spending the better part of my day migrating my projects over only to find out ".svelte" files are not packable, so I'll need to have at least 2 node runtimes installed. That's annoying.

Mmm what's the issue here? Packaging you library for JSR? Installing a library containing a svelte file in a sveltekit appthat you want to run with Deno?

The former. It seems to be what's described here: github.com/sveltejs/sve... I imagine there's a workaround to this by adding a step to compile the svelte files to .js files but I'd done enough debugging for the time being to get into that.

Compiling to JS is also wrong because it means they will ship with their version of the compiler (or fail if they are mounted in the wrong runtime). Will see if we can do something about this.

Oh awesome, lmk if there's anything I can do to help! The caveat to this is that I actually had no intention of uploading to JSR, but it seems that Deno's `pack` only prepares for JSR, afaik.

Mmm you could publish to npm and have it available in Deno via `npm:`...but then as you've said you would need the npm/node binary. But would you only publish on jsr then?

I actually intend to publish to a private npm compatible registry, and I'm not sure if JSR packages are cross compatible, I've never worked with JSR before actually. Importing from there is no issue, but generating the tarball for it doesn't seem to be possible with Deno.