Tim

4.7K posts

Tim banner
Tim

Tim

@tpillard

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

Paris, France Katılım Ocak 2012
908 Takip Edilen602 Takipçiler
Sabitlenmiş Tweet
Tim
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-se…
English
12
52
235
91.5K
Tim
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.
English
0
0
1
93
Tim retweetledi
React
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:
React tweet media
English
5
12
78
8.4K
Hacksore
Hacksore@Hacksore·
this lil button is cute
GIF
English
5
11
223
85.2K
Tim
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. github.com/swc-project/sw…
English
0
0
0
77
Tim
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.
English
1
0
1
28
Tim
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 github.com/viteup
Tim tweet media
English
2
1
2
305
Tim
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).
English
0
0
0
25
Grégory Houllier
Grégory Houllier@ghoullier·
@tpillard @dashlane With tsup, we faced runtime issues with the way it transpiled decorators. With tsc, it's a pain in the ass to sucessfully configure dual build.
English
1
0
1
46
Tim
Tim@tpillard·
btw viteup@0.0.5 & vite-plugin-swc@1.1.0 coming later today hopefully with a bunch of improvements & latest dependencies upgrade
English
0
0
0
56
Tim retweetledi
Stephan Meijer
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"
Stephan Meijer tweet media
English
72
30
877
103.5K
Tim
Tim@tpillard·
@WebReflection Some other SW-based variations seem possible.
English
1
0
0
27
Tim
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.
English
1
0
0
37
Andrea Giammarchi 🍥
Andrea Giammarchi 🍥@WebReflection·
the CSP inegrity paradox: there's no way from your own script to validate this expectation: if (document.currentScript?.integrity !== 'sha384-blah') throw new Error('Unauthorized'); that would make the script aware of itself being "hacked" somehow but you can't put sha in sha
English
1
0
4
418
JLarky
JLarky@JLarky·
@yeedle @mootoday Speed is a concern, it should be 0 seconds for both commits and pushes
English
1
0
5
151

Keşfet

@hardfist_1 @rspack_dev @Hacksore @ghoullier @dashlane @next @WebReflection @elonmusk