Tim (@tpillard) header
Tim (@tpillard) profile picture

Tim

@tpillard

Web | Platform Engineering - Staff Software Engineer @dashlane - ex @gandi_net @tpillard@hachyderm.io

 Paris, France
timtech.blog
Joined January 2012
  • Tweets4.7K
  • Following926
  • Followers596
342Media
Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by Tim (@tpillard)Photo by 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? timtech.blog/posts/react-ser…
React Server Components, without a framework?

React Server Components, without a framework?

Can we use React Server Components today, without a framework like Next.js? As our experiment shows, not without significant challenges - for now at least?

timtech.blog
12
52
9
235
91,591
Dusting off my blog (~stale since 2023) & some new blog posts coming Q4
1
1
2
110
Work in progress, stay tuned!
10
Tim retweeted
Tim (@tpillard) profile picture
Tim@tpillardOct 25
Dusting off my blog (~stale since 2023) & some new blog posts coming Q4
1
1
2
110
Rspack 2.3 will use SWC Next for JavaScript parsing. We plan to gradually migrate more of Rspack's internals to SWC Next and introduce a new swc-next-loader that supports custom transform plugins written in JavaScript.
Jiahan Chen (@jiahan_c) profile pictureJiahan Chen
@jiahan_cOct 28
SWC Next is here! Today, customizing how your code is transformed often means using Babel plugins or writing Wasm plugins for SWC. I believe the next generation of JS compilers should combine Rust's performance with the flexibility to write custom transform plugins in JavaScript. SWC Next's flat AST enables efficient data exchange between Rust and JS, laying the groundwork for fast JS plugins 🚀
Image from Jiahan Chen (@jiahan_c)
4
10
2
103
6,021
Thank you to everyone who provided feedback and guided me in the right direction for this, truly appreciate it! cc @dotproto @oliverdunk_ @rewislam & others who’ll recognise themselves. :) #w3cTPAC
Tim (@tpillard) profile pictureTim@tpillardOct 24
Dashlane's experience of & feedback on Web Extensions Manifest V3 (mostly Chromium). github.com/w3c/webextensions… cc @dashlane
Dashlane's experience of & feedback on MV3 (mostly Chromium) · Issue #1144 · w3c/webextensions

Dashlane's experience of & feedback on MV3 (mostly Chromium) · Issue #1144 · w3c/webextensions

Note: this issue consolidates 3–5 years of complex work by many contributors across multiple teams; I used AI to help write it. This is Dashlane's experience of and feedback on Manifest V3'...

github.com
1
102
Tim retweeted
Tim (@tpillard) profile picture
Tim@tpillardOct 25
I will attend W3C TPAC in Dublin Oct 27 - 29. Come say hi or DM me if you want to catch up. :) cc @dashlane
1
3
123
Tim retweeted
SWC (@swc_rs) profile picture
SWC
@swc_rsOct 28
Introducing SWC Next: the foundation for SWC’s next major version, built on a new architecture inspired by Yuku. - Up to 3x faster native parsing - Up to 10x faster parsing through the JavaScript API - A flat, ESTree-based AST designed for speed, memory efficiency, and JavaScript extensibility Starting with parsing, we’re bringing the rest of SWC to this new architecture. Built together by the SWC and Rstack teams.
14
59
15
356
36,332
in an era of constrained compute (cpu and memory crunch is coming folks) it is more important than ever to squeeze every ounce of performance and efficiency out of your services, esp if you operate at a meaningful scale
21
13
12
399
57,716
Tim retweeted
Tim (@tpillard) profile picture
Tim@tpillardOct 24
Dashlane's experience of & feedback on Web Extensions Manifest V3 (mostly Chromium). github.com/w3c/webextensions… cc @dashlane
Dashlane's experience of & feedback on MV3 (mostly Chromium) · Issue #1144 · w3c/webextensions

Dashlane's experience of & feedback on MV3 (mostly Chromium) · Issue #1144 · w3c/webextensions

Note: this issue consolidates 3–5 years of complex work by many contributors across multiple teams; I used AI to help write it. This is Dashlane's experience of and feedback on Manifest V3'...

github.com
3
1
8
494
I will attend W3C TPAC in Dublin Oct 27 - 29. Come say hi or DM me if you want to catch up. :) cc @dashlane
1
3
123
Dashlane's experience of & feedback on Web Extensions Manifest V3 (mostly Chromium). github.com/w3c/webextensions… cc @dashlane
Dashlane's experience of & feedback on MV3 (mostly Chromium) · Issue #1144 · w3c/webextensions

Dashlane's experience of & feedback on MV3 (mostly Chromium) · Issue #1144 · w3c/webextensions

Note: this issue consolidates 3–5 years of complex work by many contributors across multiple teams; I used AI to help write it. This is Dashlane's experience of and feedback on Manifest V3'...

github.com
3
1
8
494
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:
Screenshot from blog post with text: How to Migrate to a Build Tool If your app has unusual constraints, or you prefer to solve these problems by building your own framework, or you just want to learn how react works from scratch, you can roll your own custom setup with React using Vite, Parcel or Rsbuild. For existing apps, these guides will help you migrate to a build tool: - Vite Create React App migration guide (link) - Parcel Create React App migration guide (link) - Rsbuild Create React App migration guide (link) To help get started with Vite, Parcel or Rsbuild, we’ve added new docs for Building a React App from Scratch.

ALT Screenshot from blog post with text: How to Migrate to a Build Tool If your app has unusual constraints, or you prefer to solve these problems by building your own framework, or you just want to learn how react works from scratch, you can roll your own custom setup with React using Vite, Parcel or Rsbuild. For existing apps, these guides will help you migrate to a build tool: - Vite Create React App migration guide (link) - Parcel Create React App migration guide (link) - Rsbuild Create React App migration guide (link) To help get started with Vite, Parcel or Rsbuild, we’ve added new docs for Building a React App from Scratch.

5
12
3
78
8,449
❤️
htmx.org / CEO of Customer Disposal (same) (@htmx_org) profile picturehtmx.org / CEO of Customer Disposal (same)
@htmx_org12 Jan 2025
a subtle drop shadow indicating depth... a clear mouse over affordance... click action w/a skeumorphic change in height... this could be us
1
200
this lil button is cute
5
11
4
218
85,330
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) profile pictureHacksore
@Hacksore12 Jan 2025
this lil button is cute
24
140
5
3,517
83,033
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. github.com/swc-project/swc/p…
chore(ci): Add `vite-plugin-swc-transform` to ecosystem-ci by tim-pillard · Pull Request #9834 ·...

chore(ci): Add `vite-plugin-swc-transform` to ecosystem-ci by tim-pillard · Pull Request #9834 ·...

Description: Add vite-plugin-swc-transform to the ecosystem CI.

github.com
101
[email protected] npmjs.com/package/viteup
1
101
[email protected] npmjs.com/package/vite-plugi…
71
We were stalled with tsup to ship dual build of packages with TS decorators. Viteup solved our issue. Thanks @tpillard 👏
Tim (@tpillard) profile pictureTim@tpillard28 May 2024
Looking for people / early adopters willing to play with (or let me play with) an experimental build system based on Vite + SWC (opt-out) for library type JS / TS (ESM-only) packages, for feedback. Even better if want CJS + ESM > ESM-only. It works in prod. OSS is bonus.
1
1
3
236
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 github.com/viteup
Image from Tim (@tpillard)
2
1
2
321
btw [email protected] & [email protected] coming later today hopefully with a bunch of improvements & latest dependencies upgrade
68
Load more