3 ms·
It was React. Code in React's repository had to be patched to fix this. Next.JS just happens to be the biggest user of this part of React, but blaming Next.JS
by tempaccount420 10mo ago
It was React.
Code in React's repository had to be patched to fix this.
Next.JS just happens to be the biggest user of this part of React, but blaming Next.JS is weird...
- cryptonym 10mo agoThanks, that's what I acknowledged in the message you just replied to. I'm not blaming anyone. Mostly outlining who was impacted as it's not really related to the front-end parts of the framework that the initial comment was referring to.