LightningCSS, I don't understand. Postcss takes 150ms for a sizable project, esbuild minifier < 100ms. Is there a situation where this is a major problem? Also, no plugin / config compatibility with anything. Not sure I'm sold on this one.

Sometimes you see a post, and it's clearly engagement bait, but it's so delicious you just can't resist eating it. Yum. Really, I respect that.

Management pro tip: we try not to call people "resources" when they're around. If you slip, say: "oh no Piotr, we mean your *time* is a valuable resource, not you the person"

Having completed 6 soft skills trainings, I'm ready to help you with code reviews. Instead of: > pointer-events: none break button Say: > Great job building this button! It seems to have a click issue, so you could make the button even better by fixing it. Feel free to reach out if you need help!

OK I think I solved the barrel file problem! 1. Only expose the barrel (not 3K deep modules) in package.json exports to please TS 2. Use vite plugin to look into the barrel and rewrite barrel import to deep imports 3. Use relative imports to bypass package.json exports check Should work

If you remove a function from the public API, but you're 100% sure nobody used it (e.g. you can inspect all the consumer code for an internal lib, or you have telemetry), is this a breaking change?

Ooh I'm in such a grumpy mood this evening, I could go on grumping for hours, which means it's about time to close 💻 and open 🍺

Speaking of frontend urban legends When someone says more SSR improves load timings people kinda go "oh but of course it does" In fact, it's not obvious SSR always outperforms CSR, like have you never seen a slow DB query or faulty backend service, maybe my backends are especially bad?

Everybody's saying barrel files bad, avoid barrel files, but nobody told me typescript gets very upset (like 20 seconds per autoimport upset) when you feed it 3000 separate modules

Ever had an interview so tense you were actually ready to pay a bit extra just to never deal with the hiring manager again?

American friends who hurt without TikTok From Russia with love, it's time you met the mighty VPN

One of my worst career experiences was job seeking while struggling with depression. Nobody wants to hire someone with zero energy and a very negative attitude, and each rejection makes you more negative, and it kinda spirals. Not recommended.

Got some kind of a hobby, renovating this apartment. Can't say I enjoy it. But hey, at least it stops me from thinking about programming!

If you're using JS for anything data-related, and it doesn't strictly have to be in JS for production reasons, you're really doing yourself a disservice.

I noticed bluesky removes bot followers, but leaves them in follower count. Wonder if it's a genuine bug, or something they "overlooked" to make the place feel livelier

Whenever I hear GPT will take over our jobs blah blah, I go to our Jira. It has feature requests like "make the wiggle do wiggle wiggle" and support requests with "app don't work please halp" and I feel pretty safe.

Ran some vanilla community detection on npm packages, very cool how it discovers e.g. polyfills, or eslint plugins by topology only. But now a large ecosystem can "capture" generic utilities it depends on, e.g. aws-sdk captures tslib, jest captures chalk. Maybe if I feed it more data...

Working on something fun! This are the top 3000 npm packages and their dependencies. We can see constellations of babel (green "bush" on the right), aws (red / pink blob on top), etc. Wonder if I can scale and cleanup this to see anything useful.

I really hope we'll leave the cjs vs esm war behind someday. It'll be something to scare junior devs, "at your age I had to wrap every file into a function so that I had something to eat" kind. Someday, just not yet.

Ok, been on bluesky for over a week now, and I don't hate it so far.

State of npm, p7 Finding an npm package to solve a specific problem is hard. Npm is a trash bin, StackOverflow is dated, GPT hallucinates, social hype is gone when you need it. GitHub — ur best bet, but not perfect. Why is your average e-commerce better at suggestions than entire JS ecosystem?

At last, 10 years into my career, my first open-source contribution. Tweaked some caches in browserslist, speeding it up 12x in our project's build. Thanks to @en.sitnik.ru for swift reviews and releasing it! github.com/browserslist...

On a positive note, I haven't seen any BS content on whose UI framework is better in a while Either we've moved part that, or react has won this war.

LinkedIn is not very pleasant, but right now it has the best balance of user base size and a decent algorithm that amplifies your content, even on a free tier, so it's a platform not to ignore.

State of npm, p6 Rockstar developer cult is strong in OSS. Once you see code in node_modules as a gift from gods of programming: - you feel you're not good enough to contribute - or, to *become* a god of programming, you create new projects over helping existing ones Bad mental model.

Man this open source thing is really broken, I'm at part 7 of whining and no end in sight

State of npm, p5 You see a bug in lib A, fix it, send MR. Nobody comes. Maybe herding sheep in Patagonia, maybe dead. No blame for being dead. Options: - patch-package (thx @davidsh.bsky.social) - Use library B - Fork library A Now your fork must fight fight lib A. Hello package proliferation.

State of npm, p4 Magic combo of easy publishing and hard maintenance means that >90% of packages are garbage — not malware or spam, just not usable due to ⚠️ packaging errors 🪲 bugs 🤪 poor docs With no built-in way to tell garbage from a good deal, we turn elsewhere to differentiate them...

State of npm, p3 Publishing an npm package is so easy you can use npm for free file transfer / sharing. You'll need: email and a package.json with name and version. Put anything you want (it's funny dogs) to the folder, npm publish, et voila you can npm i it from any machine and get funny dogs.

State of npm, p2. JS ecosystem is evolving — good, but a pain for maintainers. You can't just put your cute 100-line lib to npm, you must - add TS - now go fight require vs esm war - now, support import maps - also, wrangle breaking changes in your dev deps No peace for the wicked.

State of npm, p1 I hear npm has 3 million packages. Good for an app developer: you can focus on the app, not the plumbing. For an aspiring open source author, not so fun. Unless you have a genius new way to solve a problem, you only have incremental improvements of existing libraries to make.

Self-introduction: 👴 Doing frontend since 2015 👨‍💼 Hopping around Russian big tech since 2018 🧑‍🏫 Built funky React stuff for a UI kit of a 50M+ DAU service ⚛️ Haven't touched React since 2022, no regrets 👷 Tech lead / engineering manager for 3 years now ✍️ Blogged a bit on thoughtspile.github.io

This bluesky is like old twitter without ads and pay-to-win, am I right?

OK my friends, old and new, this one looks livelier than masto, let's try here! I've been a bit pressed down with job and life for the last year, but maybe I can put a little something together in the holidays, so hop in.