Trying my best ✨cool profile pics like yours help a lot 🫡
07.02.2025 01:48 — 👍 2 🔁 0 💬 0 📌 0@wunderacle.bsky.social
doing code at @HubSpot, some governance at the @openjsf, @webpack TSC; dabbling at @nodejs’s infrastructure
Trying my best ✨cool profile pics like yours help a lot 🫡
07.02.2025 01:48 — 👍 2 🔁 0 💬 0 📌 0node:pdf when? (Just kidding)
07.02.2025 01:45 — 👍 0 🔁 0 💬 1 📌 0@notwes.bsky.social oh hi Wes, just wanted to randomly say your profile pic is cool. That’s it!
07.02.2025 01:45 — 👍 4 🔁 0 💬 1 📌 0I appreciate the care here :)
28.01.2025 13:33 — 👍 2 🔁 0 💬 0 📌 0Oh yes, sorry, what I meant is, a CLI flag to disable the warn at build time :)
27.01.2025 16:02 — 👍 0 🔁 0 💬 0 📌 0I see. I wish there was a way to remove the warning 🙈
27.01.2025 15:36 — 👍 0 🔁 0 💬 1 📌 0Well, yes and not. Again, Next also contains a lot of powerful things out of the box. There is also Nextra nextra.site which is exactly like 11ty but based on Next.js
Technically speaking both 11ty and Next.js are huge busses; They have a lot of stuff under the hood.
Although, Vercel themselves say that most scenarios you shouldn’t need static exports… Next.js is after all a server-first framework.
27.01.2025 04:44 — 👍 1 🔁 0 💬 1 📌 0I still recommend Next.js. It does has a static export mode, and it works fine for GitHub pages and other self hosted options, although I always recommend the usage of rewrite rules as they will be needed to handle the .html to extensionless rewrite.
27.01.2025 04:43 — 👍 0 🔁 0 💬 2 📌 0We aint bundling components. The UI packages will just have the raw components. There is no reason to add a bundler there.
26.01.2025 01:39 — 👍 2 🔁 0 💬 0 📌 0Sorry, what are you referring to? 🤔
26.01.2025 01:23 — 👍 0 🔁 0 💬 1 📌 0I just rather separate App logic and make the components easier to read and maintain and leave styling as its own thing.
26.01.2025 01:17 — 👍 0 🔁 0 💬 0 📌 0I’m completely fine with Tailwind’s default way of a “wall of classnames” — can be pragmatic for Git diffs and Prettier sorts it by default (as it does on CSS components)
26.01.2025 01:16 — 👍 0 🔁 0 💬 1 📌 0And IMO I prefer the separation of concern of styling vs component logic. Technically speaking, it even allows multiple different stylesheets (if I’d like to wire some).
26.01.2025 01:16 — 👍 0 🔁 0 💬 1 📌 0To be fair, not against a change. But nothing justifies right now abandoning what we have; I won’t recommend a refactor of how we do styles if so far the DevEx has been great.
26.01.2025 01:15 — 👍 1 🔁 0 💬 1 📌 0But that is not @apply’s fault, that is how CSS components work. The bundler wire those as generated unique class names.
26.01.2025 01:14 — 👍 0 🔁 0 💬 1 📌 0Not sure I get your concern. The components on their UI package have the exact same styling.
26.01.2025 01:11 — 👍 0 🔁 0 💬 1 📌 0Now, is it the intended way by the maintainers? Very possibly not. Does it work very well for us? Absolutely yes.
25.01.2025 23:54 — 👍 0 🔁 0 💬 0 📌 0Also, we justify our usage of “apply” on the same doc at the bottom, and it works perfectly fine for us and it is honestly a surprisingly easy DevEx.
25.01.2025 23:53 — 👍 1 🔁 0 💬 3 📌 0Augustin, I ain’t going to change the whole website CSS because of some random Bluesky thread lol
25.01.2025 23:50 — 👍 3 🔁 0 💬 3 📌 0Deno is committed to web standards - that's why we co-founded WinterCG two years ago. Today marks the next step in that journey: WinterCG moves to Ecma International as technical comittee 55 (TC55).
Goodbye WinterCG, welcome WinterTC!
deno.com/blog/wintertc
IMO it is a good take.
15.12.2024 14:46 — 👍 2 🔁 0 💬 0 📌 0a list of languages the nodejs.org site needs to translate yet Spanish Italian Japanese German Russian Portuguese, Brazilian Romanian Greek
Are there any folks in the @nodejs.org community interested in taking a slightly more active role in internationalization efforts?
We have a number of languages in need of proofreaders, and even language coordinators that can resolve questions/approve suggestions, etc.
Here's our biggest needs:
Approachable Open Source by Brian Muenzenmeyer
Abby holding the book, pointing to her endorsement
"Approachable Open Source by Brian Muenzenmeyer is a culmination of wisdom earned in the open source trenches. This book is a beautiful exploration of humanity in open source, serving as the perfect companion for finding your community in the often intimidating world of open source software. Essential reading for front-end developers looking to level up as contributors and maintainers. Brian has written the open source manual that maintainers have been waiting for." — Abby Cabunoc Mayes, Open Source Leader at GitHub
Just got my copy of @approachableopensource.com by @bmuenzenmeyer.bsky.social — such a thoughtful guide for anyone navigating open source! Thrilled to have shared my thoughts on the back cover. 🎉
What’s a resource that’s inspired your open source journey? Let’s share favourites!
Ikr?
01.12.2024 15:39 — 👍 1 🔁 0 💬 0 📌 0The character style and plot is definitely so Toriyama-eskee
27.11.2024 14:52 — 👍 1 🔁 0 💬 0 📌 0Last episode was the wildest shit ever. I was just holy shit. Had a blast, had fun. But that’s not how things work and maybe would work… (except the part of universe simulation, that could indeed happen lol)
27.11.2024 14:23 — 👍 1 🔁 0 💬 0 📌 0So some stuff was kinda accurate and loved the tech terms but then a lot of shit was just fantasy and wtf, and the more episodes passed the more wtf it became.
27.11.2024 14:22 — 👍 0 🔁 0 💬 1 📌 0Like how they achieved to have a mind processing like in a local computer; or have these minds penetrating firewalls and stuff; It doesn’t matter how much processing power you have, if there is not vulnerability there, it ain’t happening.
27.11.2024 14:22 — 👍 0 🔁 0 💬 1 📌 0I’ve finished watching this anime from AMC “Pantheon” — one of the craziest tech anime I’ve seen in a while.
The beginning was accurate in a few terms, but then it became more and more bending tech rules that it entered sci-fi realm.