David Bushell

Are you providing any config options to the adapter in `svelte.config.js`? Are you getting any other error logged before this? If there are earlier errors the build is incomplete. If...

That's good, you can ignore the first error. If the build is OK you can manually delete `build/server` or just ignore it. Those files get bundled into `build/server.js`. The error...

Yes true I should probably be using [`path`](https://nodejs.org/api/path.html) that handles the OS/Windows differences. Not sure if that would change anything because all the other paths are working in the build....

Thanks for the suggestion! Originally this was going to be a PR to the existing adapter. I added my notes to the [related Deno Deploy issue](https://github.com/pluvial/svelte-adapter-deno/issues/40). My "fix" ended up...

@jpaquim I'm in a similar position I'm not doing much Svelte Kit lately. So I may not be able to maintain anything going forward! I think it's fine though to...

Honestly I'd suggest using the official node adapter if it works. The Deno > Node compatibility layer shouldn't be a concern. From what I understand it's largely a thin layer...

Hi can you provide the full Error? Your output is missing the start of the error. It sounds similar to this: https://github.com/sveltejs/kit/issues/4873 You can't use `getClientAddress` during the build/prerender. You...

There are scenarios where the "slow types" requirement/error is far too onerous. For example, requiring an explicit `void` return type on a function that has no `return` statement. Personally I...

> Instead of server side, why not run `tsc` on the client side. Server side doesn't need to generate compatible layer for npm. The `jsr` cli in the client handles...

> Maybe we can make this a fallback for unsupported slow-types. I think the suggested fallback is just to opt-out with the [ignore slow types](https://jsr.io/docs/about-slow-types#ignoring-slow-types) option when publishing. I don't...