4 ms·
True, thanks for sharing. Worth mentioning that's on the "full-stack" part of the framework. It doesn't impact most React website while it impacts most next.js
by cryptonym 10mo ago
True, thanks for sharing. Worth mentioning that's on the "full-stack" part of the framework. It doesn't impact most React website while it impacts most next.js websites.
- tempaccount420 10mo agoIt 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.