Mei Schoenberg

> It seems very unlikely that the code is a number. It's better to always keep ElysiaJS updated. If you want to send an internal error like this, it's better...

Ah nice, I guess I missed that (:

**update**: probably fixed by https://github.com/gornostay25/svelte-adapter-bun/commit/8140529 I ended up just doing ```ts const requestFixupHandle: Handle = async ({ event, resolve }) => { // yes this is also still necessary ....

> We don't want the browser reaching out to the server on every single request in case there's some secret route that that might match. […] We also don't want...

I think `export const private = true;` may be extraneous with fast, idempotent hooks.

So I ended up spending all of today learning enough SvelteKit internals and I wrote https://github.com/ckiee/svelte-adapter-bun/commit/94f6b0b236e3d114f875cb0f860aa1abf68a1452 as a functional PoC which avoids the most painful parts. There's no live demo...

It would have to be a global client-side-app-wide toggle to make sure they cannot recover it from the route manifest, and that just completely degrades the UX site-wide. My PoC...

a more up-to-date version of the superjson `onAfterHandle` from upthread: ```js .onAfterHandle(({ response, path }) => { // https://github.com/elysiajs/elysia/issues/262#issuecomment-2146844908 // TODO: what is this? if (ELYSIA_RESPONSE in response) { return;...

@IvanMalison Personally I still have a NixOS `services.xserver.desktopManager.xterm.enable = true;` in my config so NixOS reads home-manager's `~/.xsession`. (as described in https://github.com/nix-community/home-manager/issues/3818) Are you not experiencing the need for this...

I apologize for my last message, I think I was too tired to properly express myself - I did not mean to be aggressive. :purple_heart: Anyway, I've re-read this issue...