Tim

web | platform engineering - staff engineer @dashlane - ex @gandi_net @[email protected]

[Tim @tpillard]

New Blog Post!

A week ago, I knew nothing about React Server Components.
I've tried to migrate an existing React SPA to RSC without a framework, made a live demo / playground, and wrote a blog post about it.

React Server Components, Without a Framework?

https://t.co/0SCJRlDTfl

[Tim @tpillard]

@hardfist_1 @rspack_dev Unironically yes in many cases, as long as the absolute production build time remains within a reasonable range for the project’s complexity.

[React @reactjs]

Based on feedback, we've added migration guides from Create React App to Vite, Parcel, or Rsbuild when a framework isn't the right fit for your use case, or you prefer to continue building your own framework:

[Tim @tpillard]

❤️

[htmx.org / CEO of #Schizophreniamaxxing (same) @htmx_org]

a subtle drop shadow indicating depth... a clear mouse over affordance... click action w/a skeumorphic change in height...

this could be us

[Hacksore @Hacksore]

this lil button is cute

[htmx.org / CEO of #Schizophreniamaxxing (same) @htmx_org]

a subtle drop shadow indicating depth... a clear mouse over affordance... click action w/a skeumorphic change in height...

this could be us

[Tim @tpillard]

@Hacksore hey I recognise this one, I had a lot of fun with the first implementation in 2022

https://t.co/jsIm9OXcov

[Tim @tpillard]

I'm not sure this is still relevant, or such a humble project as vite-plugin-swc-transform applies, but I thought this was a great idea from SWC a few months ago, only didn't find the time to do it earlier.

https://t.co/ea2maRCXvS

[Tim @tpillard]

[email protected]

https://t.co/Eq0A9TH5wh

[Tim @tpillard]

[email protected]

https://t.co/Ffid2n7Vrx

[Tim @tpillard]

@ghoullier Ah, I see now, sorry the link in the first tweet is wrong.
Here’s the current repository:

https://t.co/owpBa12ZQz

[Tim @tpillard]

mkdir built-with-viteup && cd $_
echo '{ "name": "'$_'", "type": "module", "exports": "./dist/index.js" }' > package.json
echo "export const foo: string = 'foo';" > index.ts
npx viteup

https://t.co/WpAMi6XxbU

[Tim @tpillard]

@ghoullier I’ve been entertaining the idea of moving it to the Dashlane org on GitHub / npm but nothing’s decided yet & no rush.

[Tim @tpillard]

@ghoullier @dashlane Does this project also have tests?
You can use vitest & leverage the same compilation for both build & test use cases.
In which case you’ll want to use the getResolvedViteConfig() utility exported by viteup/pure (viteup/api in the @next release).

[Grégory Houllier @ghoullier]

We were stalled with tsup to ship dual build of packages with TS decorators. Viteup solved our issue. Thanks @tpillard 👏

[Tim @tpillard]

btw [email protected] & [email protected] coming later today hopefully with a bunch of improvements & latest dependencies upgrade

[Stephan Meijer @meijer_s]

OMG. Why are directives now used as decorators? Use strict, use server, use client, use cache. What else we got? I don't like where this is going. Soon they need options, and we get shit like "use cache: 5 days, but not in december"

[Tim @tpillard]

@WebReflection Some other SW-based variations seem possible.

[Tim @tpillard]

@WebReflection I guess you could have a SW which intercepts the request, compute the resulting SRI hash, compare it with the expected value provided & communicate back the result to the main thread, or serve a different resource.

It´d add a fair amount of complexity, risk and also limitations.

[Tim @tpillard]

@JLarky @yeedle @mootoday Amen