Activity for luca.schneider.is
Loading activity...
Really nice spin on the RSC concept with client-first. This way the mental model of developers can still be useful, even in the RSC era. I see why others didn't do that, as composition is a bit harder and doesn't feel as natural compared to the server-first approach. I'm looking forward to try it.
Tanner Linsley@tannerlinsley.comFinally, TanStack Start now supports React Server Components! Start's RSCs are a truly fetchable, cacheable and composable primitive that work with your favorite tools instead of dictating your entire architecture. Oh, and one more thing... "Composite Components" 😉 tanstack.com/blog/react-s...
Finally, after adding turbopack support, next-yak also supports vite (for rolldown and rollup). Additionally we published a new storybook addon (compatible with webpack & vite). Read up upon here: yak.js.org/docs/vite & yak.js.org/docs/storybook
If you don't see this, you're limiting the experience of your users.
Cody@codey.bsky.socialUnderstandable. In the end what matters is that a static CSS file served with a hashed filename and `Cache-Control: Immutable` is served to end users, with the only remaining runtime logic being what `className` attributes to use to decide styling, and the occasional custom property override 💖
@whiteshoulders.bsky.social contributed a very good PR to next-yak. It marks the beginning of our efforts to support more bundlers than just webpack in next.js. Thank you for the contribution: github.com/DigitecGalax...
www.galaxus.ch/en/page/next... Why and how we created next-yak (yak.js.org)
We found a way to run our custom SWC plugin on the client in WASM 🎉 If you want to see how next-yak transpiles your input to static CSS have a look here: yak.js.org/playground
We've released a eslint plugin for next-yak to make the migration from styled-components even easier and faster 🎉 Install it, try it and write us what you think yak.js.org/docs/eslint-...
I went from RSC lover to RSC sceptic and today as I'm unsure what to think of it, this incredible post dropped. I like it way better than the first post of dan, but I'm still not sure if the benefits of RSCs outweight the costs in all cases. The complexity and also the number of bugs is just huge.
Thanks to @jantimon.bsky.social, expect up to 20% smaller CSS files in the next update of next-yak (github.com/DigitecGalax...).
We've migrated from styled-components to next-yak at our company (galaxus.ch) and we saw ~12% decrease in INP and ~15-20% decrease in LCP due to better latency on the server. Build times didn't go up drastically and moving forward we bet fully on it. Read the docs here: yak.js.org
I got it working 🥳 Had to specify explicitely that my swc plugin (wasm) should be included. The loading of the wasm is super slow (~10s), but I'm happy that it runs. Next up: optimize the loading time. @kdy1.bsky.social any hints?
Luca Schneider@luca.schneider.isMaybe I have more luck here 😅: Does anybody have some experience running SWC as a standalone tool in a vercel function? I want to provide a playground for our SWC plugin, but that has to run on the server. It runs perfectly fine locally, but vercel has some issues with path mapping and binary sizes
Maybe I have more luck here 😅: Does anybody have some experience running SWC as a standalone tool in a vercel function? I want to provide a playground for our SWC plugin, but that has to run on the server. It runs perfectly fine locally, but vercel has some issues with path mapping and binary sizes