zachleat’s avatarzachleat’s Twitter Archive—№ 45,982

  1. …in reply to @andrewingram
    @andrewingram @fredoiq To be fair, I think this has been a problem since the very beginning—not Next.js 13