Oh look @michaelwarren.dev with @kevinpowell.co on one of my favorite topics — web components!
youtu.be/qUhtlnL48yA?...
19.11.2025 15:09
👍 37
🔁 8
💬 0
📌 0
Oh look @michaelwarren.dev with @kevinpowell.co on one of my favorite topics — web components!
youtu.be/qUhtlnL48yA?...
📚 I haven’t written much at all about the “front of the front-end” on my blog, but since I’m now working on the design engineering team @sentry.io and also maintained the design-system at adverity for some time, I have opinions there as well 😬:
Whoa. This would be incredible for frameworks like Astro. Enough to make me reconsider my dream of removing streaming support.
Finally.
✅Announcing Vitest 4.0 ✅
Our latest Vitest update brings Browser Mode to stable, allowing you to test your UI in real browsers like Chrome.
Also new:
- Visual Regression Testing to catch unintended UI changes
- Playwright Trace support for easier debugging
voidzero.dev/posts/announ...
Quest’anno é stata una gioia realizzare grafica e sito di devfest.gdgpescara.it !!!
#devfest #pescara #gdg
// -- old way export function useMyContext() { const context = useContext(MyContext); if (context === undefined) { throw new Error( 'useMyContext must be used within a MyContext Provider' ); } return context; } // -- new way export function useMyContext() { // ^^^ Ehi, naming is misleading here, it's not an actual hook! const context = use(MyContext); if (context === undefined) { throw new Error( 'useMyContext must be used within a MyContext Provider' ); } return context; }
Question for React devs: With the new use API, which isn't a hook, how are you naming your context-consuming functions?
The classic useMyContext pattern feels odd if the function is just a wrapper for use(MyContext). Does it still count as a hook, or are you using a new naming scheme?
#ReactDev
Io mi immagino che drop hanno avuto siti come quello di Aranzulla.
Fintanto che parliamo di siti di news dove è naturale che la diffusione parta dalle piazze (i social) è ok, ma quelli che vivevano di traffico passivo ora si ritrovano tutto su un riassuntino di qualsiasi AI e questo è un guaio
I heard some complaints about React batching transitions (mostly on twitter), so I jumped over to the bad place and explained why batching transitions by default is good actually:
x.com/rickhanlonii...
Chissà quanto ci vorrà prima che arrivino anche da noi visto che i nostri fondali si stanno tropicalizzando. Qualche giorno fa ho visto un vermocane (coste di Palermo)
it seems an old stuff, isn't? (main is far behind)
Alla fine ho scritto un post sull'IA anch'io
danieleirsuti.dev/blog/la-moss...
This doesn't feel right to me because it's overriding the entire Location class and "window.open" at a global level. 🤔
Is this a bad practice? Any insights from test experts?
const mockAssign = vi.fn(); const mockOpen = vi.fn(); beforeEach(() => { Object.defineProperty(window, 'location', { configurable: true, value: { ...window.location, assign: mockAssign, }, }); Object.defineProperty(window, 'open', { ...window.open, configurable: true, writable: true, value: mockOpen, }); }); afterEach(() => { vi.restoreAllMocks(); });
Today, I came across this small piece of code for mocking, but I'm not sure if it's a good approach.
The environment is #JSDOM, and the testing tool is #Vitest.
The purpose of this test is to mock "window.location.assign" and "window.open"
Test experts, help.
feel you. I tried to upgrade to version 4 in my Astro blog a few days ago, and it worked beautifully in dev but not in prod and all CSS modules disappears for some reason
Sviluppare applicazioni web frontend è difficile, stare al passo con le novità è stressante e JavaScript è sempre il problema.
C'è del vero: dovremmo rivedere il modo in cui lo utilizziamo oggi.
danieleirsuti.dev/blog/la-demo...
Maybe because most influent JS people are tech bros who likes Musk and his enlightened vision of the world.
I don't miss that place, less contents but more quality than noise
Nowadays it’s hard to imagine an endpoint without openapi spec but sadly it happens… very often.
Anyway, this is readable, I like it!
These people don’t look beyond their own garden.
Sometimes I think about how we (as collectivity) ended up like this
I'm sure is related to css modules but I'm lost 🤷♂️
Just updated my website to #astro 5.2.3 and #tailwind 4.0.3 and my css blew up 🤔
Locally it works but in production... well, not good. No clues what's happening.
live: danieleirsuti.dev
old build: danieleirsutidev-jqrie8cj8-daniele-irsutis-projects.vercel.app
it's time to shine.
now in cubital characters: D E P R E C A T E D 👀
We can’t be friends with nazis I guess 🤷♂️
Sorry, I couldn’t resist
Dear frontend users: Stop using the "custom" prefix when you have no ideas on how to name things, like:
Custom component;
customClass;
custom date;
Stop it.
Thank you.
ah this works
