wojtekmaj.pl
Dad, husband, TypeScript developer.
414 posts
389 followers
162 following
Regular Contributor
Active Commenter
comment in response to
post
Blocked! But if you hit Reply, you can see the whole thing 😅
comment in response to
post
To prawda, byłem tym kotkiem
comment in response to
post
Mine was 360€ and I got the cheapest model that had two wheels 🙄
comment in response to
post
TIL, thank you!
comment in response to
post
Yet another reminder accessibility is for everyone. I love this infographic 👇🏻
comment in response to
post
I did nazi any either.
comment in response to
post
Imagine a small, $1 fee for each.
comment in response to
post
And these numbers are from a regular, efficiency-first laptop!
My plugins:
- vitejs/plugin-basic-ssl
- vitejs/plugin-react
- vite-plugin-pwa
- vite-plugin-static-copy
- vite-plugin-simple-html
- vite-plugin-es-toolkit
- vite-bundle-analyzer
- sentry/vite-plugin
- react-aria/optimize-locales-plugin
comment in response to
post
With experimental.enableNativePlugin enabled:
App 1: 2.38s (63% faster in total)
App 2: 7.98s (61% faster)
Wh... whaaat?
comment in response to
post
Here's some stats from rewardoapp.com apps. Rolldown-Vite does improve the performance quite a bit.
App 1 (3694 modules):
6.41s -> 3.91s (39% faster)
App 2 (7527 modules):
20.47s -> 11.40s (44% faster)
Tested on Surface Laptop 7.
comment in response to
post
Well well well, Next.js not working well outside of Vercel's own cloud solution. Surprising.
comment in response to
post
I wasn't wrong!
github.com/eslint/rewrite
github.com/eslint/eslin...
comment in response to
post
I might not be the best source but I'm pretty sure they have actually - have heard of parallel linting and a full rewrite as well. Please hit me with community notes if I messed something up 😃
comment in response to
post
eslint-plugin-import was a worrying for me. After evaluation, I figured most of the issues I really cared about were double-reported; by e-p-i and TypeScript.
comment in response to
post
Heck, you can even use several, they don't check it at all!
comment in response to
post
Holy crap 💀 I just *want* Biome, you actually *need* it!
comment in response to
post
My largest Biome-powered project is about the size of Linux Kernel 1.0, or about twice the size of Adobe Photoshop 1.0. Still linting time counted in milliseconds!
comment in response to
post
I get you - not every tool is for everyone. If you prefer having tons of plugins that genuinely help you out - that's totally fine. For me, I just needed the basic TypeScript + React + Hooks, which Biome has all built in. I value its speed and minimal friction.
comment in response to
post
comment in response to
post
Not saying this is not a valid issue, but in general, the ROI of migrating to Biome has been really high for me, so while I'm aware of some of its drawbacks I still would, yeah :D Plus, noFloatingPromises rule is available in 2.0 beta already!
comment in response to
post
I firmly believe tools should work for me, not the other way around.
Biome's batteries-included approach let me drop all that noise and just build. 🚀
comment in response to
post
Don’t get me wrong - ESLint is an amazing project and we owe it so much. But maintaining it became a burden.
Plugins, parsers... You need like six for a basic TypeScript React project to even parse correctly!
I was spending more time wrestling with the config than actually writing code. 😤
comment in response to
post
I used to maintain a sophisticated, shareable ESLint config.
Tried migrating to ESLint 9 twice and failed both times. Miserably. 😵💫
Then I figured… if I’m putting in all this effort, why not just change course entirely? So I dove headfirst into Biome. And I loved it! Haven’t looked back since.
comment in response to
post
Me, already on Storybook 9:
comment in response to
post
I probably wasn't unblocked in a technical sense, my mind was unblocked though. Published 29 of my packages as ESM-only since require(esm) was shipped. 5 today. 9 to go!
comment in response to
post
I sometimes complain about my `yarn install` taking 4 seconds, and then I install literally anything else in literally any other ecosystem and I stop complaining.
comment in response to
post
git add --renormalize .
git commit -m "Renormalize line endings"
git rev-parse HEAD >> .git-blame-ignore-revs
then (for good):
git config blame.ignoreRevsFile .git-blame-ignore-revs
OR (just once):
git blame --ignore-revs-file .git-blame-ignore-revs
comment in response to
post
comment in response to
post
The weeling fhen ❤️
comment in response to
post
Słaby temat do żartów
comment in response to
post
Probably "whoever else".
comment in response to
post
Terrifying. And we only have 👍🏻👎🏻 buttons to fight it.
comment in response to
post
You're welcome
www.npmjs.com/package/volk...
comment in response to
post
Out of curiosity, which change inspired you to write this post? 🧐
comment in response to
post
Yarn was right all along for making PnP throw on undeclared dependency imports. When it launched, the state of undeclared deps was a total shitshow. Now it’s just… occasionally bad.
Yarn got all the hate because it broke sooo many setups, but it sacrificed itself for the greater good. True hero 🫡
comment in response to
post
I'm happily using it in monorepo, stupid question: what's missing?
comment in response to
post
This article was a pure joy to read and to play with 😻
comment in response to
post
Perhaps sharding could save your butt in the short run?
comment in response to
post
Szczerze mówiąc to nawet korzystając z wyszukiwarki nie znalazłem ani jednego takiego posta na Bluesky. Co innego na Twitterze...
comment in response to
post
Reviewed :) Geez, that was quite a trip 😅