Matt Kane

I had a quick look at the test failures and they _are_ caused by this PR. You can repro them in isolation by running `tsc -b packages/remix-netlify-edge`. The problem is...

Unfortunately it looks like https://github.com/microsoft/TypeScript/issues/37582 isn't going to be a viable answer. It didn't make it into TypeScript 4.9, so we won't see it til March.

The "fix" is to remove netlify-edge from the root tsconfig, so that it's not included in the typechecking step. That's all it's used for. The Deno package isn't currently typechecked...

I went ahead and added a separate PR to add typechecking for Deno. https://github.com/remix-run/remix/pull/4715

I think that test failure is unrelated, and is caused by a race condition in the main build script. The globals.d.ts file is [created and copied](https://github.com/remix-run/remix/blob/dev/scripts/copy-build-to-dist.mjs#L69) inside [a single `Promise.all`](https://github.com/remix-run/remix/blob/dev/scripts/copy-build-to-dist.mjs#L123),...

We're adding support for negative matchers. It's currently experimental, but can add it to the adapter when it's a stable. It would be good to think of which other routes...

Thanks, I can't remember. It was so many years ago.

Thanks for the report. I think the issue here is that we are incorrectly assuming that Svelte will always use a dev server. We will fix that, but in the...

Hi @kyllerss Is this a Netlify background function that you have created in `netlify/functions` (or wherever your functions live)? While SvelteKit itself is deployed on Netlify Functions, any functions that...

We'd love for there to be a way of deploying SvelteKit API routes as background functions or scheduled functions, but that would require work on the SvelteKit adapter. Certainly a...