@OliverJAsh Crikey, I hit this exact issue this week: wrote a new error boundary, spent ages trying to figure out why it “wasn’t working”, eventually did enough Googling to realise it’d be fine in prod. Unintuitive is the least of it.
Errors caught by React error boundaries still bubble up to the global error handler (window.onerror)—in dev but not in prod
IMO this is unintuitive—boundaries should act like try/catch. At the very least behaviour should be identical in dev & prod
Issue: github.com/facebook/react…
Made Biscoff blondies for the @MetroUK team on the US election night shift 😋
(I mean, that's my excuse so I don't eat them all myself...)
With a little help from the lovely people at Treehouse Bakery 🌱
Obsessed with Taiwan’s “down-to-earth” Halloween party, where you ONLY dress up as normal people in everyday situations. This is “the woman looking for a seat at food court”:
Check out the full Saturday line-up for #SPANC20, kicking off at 11:00am tomorrow with @MarinaHyde.
For the first time ever, our National Conference is completely digital, and completely FREE.
Register now: spajournalism.com/spanc20register
@MattieTK@iaincollins I had all the tasks printed for me for the data viz role and the code was accidentally included for one of them. Let me tell you for free, 20 pages is not a large amount 😰
A really special day for us at Habito as we announce our £35m Series C and become a certified B Corp - putting people and the planet on the same level as profit 🎉🤗🥳
@BCorpUKtechcrunch.com/2020/08/12/hab…