@healeycodes Great write up, thanks for sharing!

@mettinparzinski Hey! Sorry haven’t check Twitter in a while. You still having issues? For most folks (all) who used it and got in touch with me it worked so far.

Valve casually dropping yet another top notch documentary

Holy cow he’s back

@_chenglou A kitten dies every time my pinky finger tries to reach for tab to complete a sentence in a note taking app or when writing docs

Random notes on handling CORS and opaque responses in Service Workers:

@rspack_dev I think I reported like 10 issues so far to them, and, even if most of them were actually either edge-cases of our big app or SWC-related bugs, I got an answer within a few hours. And the couple of real bugs that were on their end were fixed and released within a single day.

Wrote a huge ass codemod (JSCodeshift + TS compiler api) to kill barrel files from the codebase with gpt 4o and (mainly) claude, took several prompts but feels good

RT @ScriptedAlchemy: I have published a blog on: "Custom chunk optimization and tree shaking" - It details how code splitting and tree shak…

@Baconbrix Yeah I feel “use dom” could def be a game changer. Especially the more RN becomes a “universal” framework (vs a “mobile” one). Great work on that too.

I still remember the painful migrations between the various routers: the old built-in one, react-native-router-flux, react-navigation and the native navigation, etc. 🫠

@brianbriscoe_ Nice write up! I noticed it’s hard to rank high on HN with framework/lib-specific articles. Don’t give up!

TL;DR: avoid the waterfall effect caused by route-based lazy-loading by preloading page chunks. In the post I’m using a custom rsbuild plugin to do it because I’m a @rspack_dev fanboy but it’s compatible with Webpack too.

Wrote something about preloading network requests in SPAs:

Just noticed this. Looks like corepack is being moved out of node? Bummer :(

@ScriptedAlchemy Yeah. I was thinking to build a plugin that creates the script resources to preload using a match between the webpack magic comment for async routes and their URLs (same matching that would be consumed by React Router in my case). But you're right, it'd be 100% custom anyway 🙃