#GETRequest
Just published Waku v1.0.0-rc.4! ⛩️

Still refactoring some internals, but it's mostly stable. Give it a shot.

github.com/wakujs/waku/...
Release v1.0.0-rc.4 · wakujs/waku
Continues refactoring some internals and deprecating some unstable functions. Migration Guide unstable_getRequest becomes getRequest. unstable_getHeaders is gone (use getRequest().headers). What's ...
github.com
October 22, 2026 at 6:32 AM
SvelteKit 3 Released
Discussion | hackernews | Author: thunderbong

#Frontend
SvelteKit 3 Released
Major Changes breaking: move remote function types to $app/server (#16740) breaking: remove experimental.handleRenderingErrors flag (#16265) breaking: make getRequest and setResponse synchron...
github.com
October 1, 2026 at 8:36 PM
@jimluther Left: "Wow this works great on PPC, and I'm handling the A5 stuff on 68k for any future changes this is great and so easy to do”

Right: 4 hours later, whittling everything down to get it to work at all on 68k, I'm not even using globals anyway who […]

[Original post on bitbang.social]
April 4, 2026 at 3:53 PM
It's more common when there's more than one property. `({ user, body, message } = getRequest());` is much nicer to read than `const request = getRequest(); user = request.user; body = request.body; message = request.message;`.

That said, yes, I also use destructuring for a single property.
February 23, 2026 at 6:30 PM