TanStack Query, and any framework with an async computed or memo, already proved the API surface. IMO the missing piece is the compiler deriving the dataflow graph.
I think a go-to future data fetching pattern will be deriving the benefits of loaders at compile time.
I've played with this enough to think it's very promising. The render-as-you-go model is more intuitive, and it solves the waterfall problem.
Yuku's analyzer is quietly one of the biggest unlocks for TypeScript in years.
Nobody has really touched semantic analysis mainstream and the React implications alone are huge
AI interaction design is so far behind that I've now started working on a harness for it.
No more magazines π§Ύ
In particular a vision system similar to Tesla FSD.
Meet OXC for TSRX
TSRX: the successor to JSX
OXC: the fast Rust toolchain powering Vite and Rolldown
Linter, formatter, parser. All compatible with your existing toolchain, including Vite.
@bruvimtired Vitest browser mode for agentic component and hook testing, Witness (https://t.co/3N9v3SsSii) for cases like HMR, network testing (like preloading), and then Playwright or something similar for full flows that typically involve backend work in between.
@qwuide@trueadm Can't speak for the spec, but on the oxc side it's already in practice. the appendix shapes are what we ship, and plain JS / TS is through oxc-parser underneath.
For pure speed I want to add yuku support going forward too. cc @arshadyaseeen .
Agreed, standards are close π
Read more and install: https://t.co/yl7bPvGraw
Architecture deep dive coming in a follow-up post. There's a reason this works without forking the toolchain.
This isn't just syntax support:
- type-aware linting
- custom lint plugins
- formatting
- standalone parser
Some examples (excluding the parser). Use your existing config.
the state of AI design tools is wild
- Claude Design: cannot generate assets, cloud-only, backed by billions
- Paper: rigid layouts, but MCP + desktop app earn it second place
- pen . dev: free, and better than both π