If you’ve ever needed to break up a long JavaScript task to keep the UI responsive, you’ve probably reached for setTimeout(). Turns out there are a boatload of other options at your disposal, like scheduler.yield(). I wrote about a handful & their tradeoffs:

@briancoords Congrats!

@howertonjosh That was a great sermon.

This is real. 😳

@mehulmpt @kettanaito @bunjavascript Confirmed - I'm not able to set either of the two forbidden headers here. Node 22.6.

@wesbos respect 🫡

@jappleby *tweets the ~80k-follower account*

@mehulmpt @bunjavascript Really! I’m assuming you were using fetch() w/ Node? I assumed you could set what you want there. cc: @kettanaito

@kettanaito Good distinction! A web security thing. You can also set them via curl.

@jacobmparis Then I’ll just tuck that useless knowledge away to impress the grandkids

@jacobmparis wat. that’s actually real???

Update: I am an idiot.

And there it is!! Right there in my EventServiceProvider.php. What a nice, refreshing face-palm moment.

@aarondfrancis Yes 👍 The route as a whole is working just fine. Getting 200s consistently. It's just that stinking event that won't seem to fire.

I've also tried manually registering a listener with Event::listen() in my AppServiceProvider, but that seems pointless if the event isn't getting dispatched anyway.