Conduitry
Conduitry
The error appears to be here: https://github.com/sveltejs/kit/blob/67e2342149847d267eb0c50809a1f93f41fa529b/packages/kit/src/runtime/server/page/respond_with_error.js#L74 The `respond_with_error` function is only including the main layout and the error layout. I haven't been able to sort through what the regular...
I believe this can be partly worked around, at least in the 404 case, by adding a dummy `[...catchAll].svelte` component: ```svelte export function load({ url }) { return { status:...
This is asking for a way to expose data from the underlying Express `request` object. It wouldn't be affected by recent changes, which still just give you access to the...
IMO your endpoint should be responsible for returning something that can be serialized (as-is) to JSON. If you're returning something that can't be losslessly serialized and deserialized, that's not something...
I'd be in favor of testing for serializability in dev mode only, and just passing along the object as-is in prod mode for SSR.
This was addressed by #5987 and will be addressed moreso by #6318.
Related: #1530
If you're doing that, it sounds to me like it should be your responsibility for just deserializing it yourself. That sounds an awful lot simpler than telling SvelteKit how it...
> That's only a solution if access to that server data is _always_ through the matching SK front-end. > > Maybe you have other apps or components that would like...
`nth_identifier` sounds like _exactly_ what you are looking for. If these various VS Code extensions don't expose a way to use that option, there's nothing Terser can do about that....