Play with @rolldown.rs in the browser via WASM with Module Federation support.
rolldown-browser-jade.vercel.app
Is the first instance of Module Federations built all in browser via WASM thanks to Rolldown!?
Play with @rolldown.rs in the browser via WASM with Module Federation support.
rolldown-browser-jade.vercel.app
Is the first instance of Module Federations built all in browser via WASM thanks to Rolldown!?
Codegen tools using @tailwindcss.com:
- V0
- Bolt
- Stitch
- Figma Make
Codegen tools using inline styles:
- Framer Workshop
Codegen tools using traditional CSS:
- π¦
Next token prediction demands co-location of styles... CSS-in-JS won for LLMs for the same reason it's better for people.
A @lambert.fun is an amazing asset.
Why don't React server components support even a one time use of React context in the same way rendering to HTML does?
I've only seen people do this using one of the myriad `react-server-dom-<bundler>` packages... github.com/facebook/rea...
Will that produce RSC? Looks like it produces a stream of HTML?
Thanks!
Is `react-server-dom-webpack` still the best way to create RSC payloads directly?
With the recent Safari 18.2 release, WebAssembly Garbage Collection is now available in all the major browsers π₯³
Iβm speaking from ignorance on that and would love if thatβs true! Gotta adopt it on our code and see!
It depends on the expense of those renders whereas selectors tend to be drastically cheaper. I think Reduxβs useExternalSyncStore and hooks implementations are good evidence of that.
In our case, a single context update without granularity could mean tens of thousands of renders. And if those renders are higher order components their reconciliation cost is multiplied... Sounds like the team is going to stick with the compiler bailouts in render rather than granular context read?
I wish you could see the sorts of things we've had to do to squeeze performance out of React at Webflow. Granted we're running a web app within a web app... but many of our unit tests leverage counting to ensure that optimizations aren't broken over time.
Really excited about compiler for us.
Tie your hands to free your AI.
Would really love to get granular updates from context updates. I remember seeing the idea of memoizing within use calls?
And if you tag it @deprecated in the comment VSCode will strike through all the references and imports.
Great stuff @kentcdodds.com !
AI traps: Lessons from launching Webflow's AI Assistant.
Another great post from @webflow engineering! πππ
webflow.com/blog/launchi...
Hey thanks for sharing!
Claudeβs MCP already has file system and SQLLite implementations! If OpenAI adds support for this Iβd be so stoked!
Model Context Protocol for standardizing how AI tools access context. Looks like LSP only for model context. Love it. www.anthropic.com/news/model-c... github.com/modelcontext...
Weβre up to 125 on the #webflow starter pack, seems like people are still arriving, give this a boost to help them find the community! go.bsky.app/Tij44E5
By the time I'm done on this planet it'll all be archives of shame... π
I am so proud of the work we've done at Webflow building a programming language that is visual-first. I got the chance to write about some of the traits a language needs to support a No Code experience on our engineering blog here: webflow.com/blog/webflow...
Reimplemented www.merrickchristensen.com from Gatsby/Styled Components -> Next.js 15/Tailwind CSS. Wanted a project that kicked the tires on server components end to end. Delighted by how comprehensive Next's support for RSC really is... Glad someone fully bet on that technology.
Right now, Bluesky feels like the early days of Twitter. Back before everyone was just trying to sell something and we could just talk about the craft.
So happy to see so much of the community here!