David Bushell

> `declare module` doesn't work even with ignore slow-types. I thought compile on client may solved the problem? Oh I see, I've no idea about that, sorry. Hopefully the Deno...

A search for the Deno standard library "@std" show: The full results page prioritises: - A package with zero score and no documentation - An unofficial “All-in-one mirror of Deno’s...

> Let us be clear: **Deno is not removing HTTP imports.** > https://deno.com/blog/http-imports Deno is supposedly committed to supporting HTTP imports. Or at least not removing them. With the Deno...

This is a good idea thanks. It is already possible to use a file URL like: ```js parse('file:///path/to/file.xml'); ``` but yes I agree also accepting a `ReadableStream` makes sense. I'll...

Yeah paths can be a bit confusing! This gets passed to `fetch` which in Deno accepts `http:` `file:` and even `data:` URLs. I've started a new branch and draft PR...

This is now implemented in v0.6.0. Apologies for taking so long!

Yes this can work on Deno Deploy the example is doing so: https://sveltekit-adapter-deno.deno.dev/ Deno Deploy has a lot of weird support conditions so it just depends what packages and APIs...

Maybe "boilerplate" is the wrong word. I mean just having built-in methods would be less of a chore than importing from `@std/encoding`. Especially when writing temporary code in the REPL.

This issue is that Deno Deploy cannot dynamically import modules. Rollup generates code like: ```js const component = async () => (await import('./_page.svelte.js')).default; ``` The `await import('...')` throws an error...

I'm working on a Deno Deploy compatible adapter here: https://github.com/dbushell/sveltekit-adapter-deno Based on the code above but with a few fixes and improvements.