Lightnews — Scholar-powered news

Reposted by Daniele

Tony Ward

@tonyward.dev

Oh look @michaelwarren.dev with @kevinpowell.co on one of my favorite topics — web components!

youtu.be/qUhtlnL48yA?...

How to use Web Components, and why you'd want to

YouTube video by Kevin Powell

youtu.be

November 19, 2025 at 3:09 PM

Reposted by Daniele

Dominik 🔮

@tkdodo.eu

📚 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 😬:

Tooltip Components Should Not Exist

A look at why tooltip components are often the wrong abstraction in design systems, leading to accessibility issues, misuse, and inconsistent user experiences.

tkdodo.eu

November 17, 2025 at 6:23 PM

Reposted by Daniele

Matt Kane

@mk.gg

Whoa. This would be incredible for frameworks like Astro. Enough to make me reconsider my dream of removing streaming support.

Firefox for Web Developers @webdevs.firefox.com · 19d

Out-of-order HTML patching, another proposal from TPAC, lets HTML be presented non-linearly, and a single file can update multiple parts of the page.

Would this feature be useful to you?

November 19, 2025 at 6:09 PM

Daniele

@danieleirsuti.dev

Finally.

Manuel Matuzović @matuzo.at · 27d

“GitHub no longer uses toasts because of their accessibility and usability issues.”

Music to my ears!

primer.style/accessibilit...

Toasts

GitHub no longer uses toasts because of their accessibility and usability issues.

primer.style

November 18, 2025 at 8:16 PM

Reposted by Daniele

VoidZero

@voidzero.dev

✅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...

Announcing Vitest 4.0

Vitest 4.0 is released with Browser Mode being marked stable, Visual Regression testing support, and Playwright Trace support. The Vitest team will focus on performance improvement in the upcoming…

voidzero.dev

October 22, 2025 at 3:47 PM

Daniele

@danieleirsuti.dev

Quest’anno é stata una gioia realizzare grafica e sito di devfest.gdgpescara.it !!!

#devfest #pescara #gdg

Devfest Pescara 2025

Join us in Pescara, IT for our conference. Featuring distinguished speakers, workshops, and lots of fun in between. See you there!

devfest.gdgpescara.it

October 16, 2025 at 11:56 PM

Daniele

@danieleirsuti.dev

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

$// -- 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; }$

September 18, 2025 at 9:43 AM

Reposted by Daniele

Ricky

@ricky.fm

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...

Ricky 🦋 on X: "@samselikoff @ryanflorence @BrooksLybrand @vitormarkisdev Here's an example of what I mean, this is a more realistic cart where changing the cart information (quantity) transitions to a new cart total. The item total and cart total each update async. Take a second to think of what should happen if you increase the quantity. https://t.co/YXhWNuaawB" / X

@samselikoff @ryanflorence @BrooksLybrand @vitormarkisdev Here's an example of what I mean, this is a more realistic cart where changing the cart information (quantity) transitions to a new cart total. The item total and cart total each update async. Take a second to think of what should happen if you increase the quantity. https://t.co/YXhWNuaawB

x.com

August 31, 2025 at 5:51 PM

Daniele

@danieleirsuti.dev

danieleirsuti.dev/blog/chi-con...

Chi controlla le informazioni, controlla il potere

Dalle multinazionali al remote working, come le reti di comunicazione determinano chi emerge — e chi resta invisibile

danieleirsuti.dev

May 25, 2025 at 1:34 AM

Daniele

@danieleirsuti.dev

Alla fine ho scritto un post sull'IA anch'io

danieleirsuti.dev/blog/la-moss...

La mossa 37: il cammino verso l’irrilevanza

La Mossa 37 non è solo un trionfo dell'AI: è l’inesorabile cammino verso l’irrilevanza dell’essere umano

danieleirsuti.dev

April 28, 2025 at 8:57 AM

Daniele

@danieleirsuti.dev

danieleirsuti.dev/blog/come-ho...

Come ho smesso di sentirmi inadatto (grazie a una community)

Ho sempre lottato con la sindrome dell’impostore, ma una community di programmatori mi ha mostrato che il vero valore è nel confronto e nella crescita

danieleirsuti.dev

April 11, 2025 at 12:22 AM

Reposted by Daniele

Artem Zakharchenko

@kettanaito.com

Soft assertions. main.vitest.dev/api/expect.h...

Vitest

Next generation testing framework powered by Vite

main.vitest.dev

March 9, 2025 at 2:22 PM

Daniele

@danieleirsuti.dev

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.

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();
});

February 12, 2025 at 1:43 PM

Daniele

@danieleirsuti.dev

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...

La demonizzazione di JavaScript

JavaScript è una barzelletta di linguaggio, dovresti impararne uno vero per poterti definire programmatore

danieleirsuti.dev

February 7, 2025 at 9:47 AM

Daniele

@danieleirsuti.dev

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

Daniele Irsuti, frontend developer

Specializzato in applicazioni React, React Native, JS vanilla

danieleirsuti.dev

February 3, 2025 at 11:37 AM

Daniele

@danieleirsuti.dev

America RN: youtu.be/bOR38552MJA?...

Blame Canada - South Park: Bigger Longer & Uncut (3/9) Movie CLIP (1999) HD

YouTube video by Movieclips

youtu.be

February 2, 2025 at 2:28 PM

Daniele

@danieleirsuti.dev

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.

January 28, 2025 at 10:46 AM

Reposted by Daniele

Colin McDonnell 💎 Zod

@colinhacks.com

ah this works

January 27, 2025 at 1:19 AM

Daniele

@danieleirsuti.dev

@vitest.dev silently updates to v3.0.0? 👀

January 16, 2025 at 2:42 PM

Reposted by Daniele

Addy Osmani

@addyosmani.bsky.social

Must reads for web developers - how modern browsers work:

1️⃣ bit.ly/browsers-pt1
2️⃣ bit.ly/browsers-pt2
3️⃣ bit.ly/browsers-pt3
4️⃣ bit.ly/browsers-pt4

and browser.engineering a free to read book on the topic

January 12, 2025 at 11:57 AM

Daniele

@danieleirsuti.dev

I tried so hard to use astro actions to handle a silly contact form and I don't think is a good idea if you want to use it in a progressive enhancement approach because there are no (ergonomic) ways to get partial input values if something goes in error 🤷‍♂️

January 8, 2025 at 11:48 PM

Daniele

@danieleirsuti.dev

Exploring @astro.build and React form actions: is there a way to progressively enhance the form to restore filled values when a validation error occurs in some fields?

const [state, action, pending] = useActionState(withState(actions.contactMe), {
data: { success: false },
error: undefined,
});

return (
<form action={action}>
<input name="email" type="email" />
<input name="subject" type="text" />
<textarea name="message" />
</form>
);

December 25, 2024 at 2:18 AM

Reposted by Daniele

Bramus

@bram.us

Did you know it's called the View Transition API (and not the View Transitions API [plural])?

Now MDN knows too (github.com/mdn/content/...) so there's no reason to keep using the wrong name.

Learn about this and other misconceptions in this post: developer.chrome.com/blog/view-tr...