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.

7/6/26, 1:04 pm0 reposts0 likes

{🧪} +paoloricciuti.svelte

@paolo.ricciuti.me

7 June

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?

diego

@diegoenriquezserrano.dev

7 June

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.

github.comJSR registry publish fails with "Unknown module" error for Svelte components · sveltejs svelte · Discussion #16167Describe the bug When attempting to publish a Svelte component library to the JSR registry, the publish process fails with the error Expected a JavaScript or TypeScript module, but identified a Unk...

{🧪} +paoloricciuti.svelte

@paolo.ricciuti.me

7 June

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.

diego

@diegoenriquezserrano.dev

7 June

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.