João Paquim

I see this and https://github.com/appcypher/awesome-wasm-langs/issues/61 maybe being solved using some kind of tags (or symbols + legend) for the implementations, describing whether they are: - An interpreter runtime compiled to...

Previous discussion concerning this: https://github.com/sveltejs/svelte/issues/530 About the motivation, at least for me runtime performance is a non-concern in terms of switch vs if/else, it only seems to be relevant in...

Concerning the comparison, I'd say stick with existing JS semantics concerning `==` vs `===`, i.e. a switch statement should be based on strict equality `===`. Regarding fall-through, I think not...

@xkpx64 thank you for reporting this, I'll take a look. Saw a few changes mentioned in the latest https://svelte.dev/blog/whats-new-in-svelte-july-2022 but still need to update the adapter to match them.

@bradleyg Thanks for giving it a try, I'll take a look this week, I've been waiting for SvelteKit and Deno to stabilize a bit further, given the amount of changes...

Hey @xkpx64 and @bradleyg can you check if you still have the issue after updating to the latest version of this package? I updated it to work with latest SvelteKit...

@osdiab I could not reproduce your error, are you using a custom `deps.ts`? Is there a minimal reproduction you could share?

@osdiab ok so it seems you're trying to consume the dependency directly from npm/node_modules. Can you maybe try using esm.sh instead? For that package, the URL would be: https://esm.sh/[email protected]

Ah, my bad, I thought you were adding the dependency in your project, but it seems to be one of SvelteKit's deps. Do you see any difference between your example...

@osdiab @lost22git @widyakumara could you maybe provide a minimal reproduction of the issue? I've been unable to reproduce it, here is a vanilla sveltekit app using svelte-adapter-deno, if you want...