Chris Carson

I'd vote for exposing an `firebaseSsrOutputFolder` in the adapter's config, and ignore the `functions` property in `firebase.json`. ```js // svelte.config.js /** @type {import('@sveltejs/kit').Config} */ const config = { kit: {...

I'm not sure if this is the same issue, but a similar thing happens when you navigate (with Javascript enabled) to a page where a shadow endpoint throws an error....

My take: The javascript-disabled user is an edge case. That doesn't mean that it shouldn't be addressed, just that adressing it should not be central to the SvelteKit API. The...

It'd be super nice to get all route details from, say, `import { routes } from '$app/paths'`. Example of data I'd find useful ```js [ { id: '/', pattern: /^\/$/,...

> exceptions are not ideal for control flow @FedericoBiccheddu As I understand it the anti-pattern is to abuse `throw` as a `goto` to jump around rather than using a more...

@FedericoBiccheddu Let's agree to disagree. I think it's fine, as a practical matter, to throw the ball over the API boundary between my code (I'm not catching it) and SvelteKit...

This issue has turned somewhat philosophical. Totally my fault. I should have stuck to the facts in the original post, rather than succumbing to the temptation to air radical Jacobin...

I can't replicate @DePasqualeOrg's eslint errors, but the [example provided](https://github.com/sveltejs/kit/discussions/11467) is instructive. Too often SvelteKit assumes that it is the be all and end all of the application, rather than...

@DePasqualeOrg Got it. I was using the SvelteKit default eslint, which I assumed had that rule, but maybe that's because I nearly always explicitly type function returns. This has more...

I agree with @dummdidumm: > it's essentially two very separate things Submitting a GET form is just like clicking on a link. The difference between `?search=foobarbaz` and `?page=2` is nil....