Working on the reg with Next.js is .... a trip. Looked up an issue to see that it is fixed in 14.3 (we're on 14.2.3) which isn't released yet. But when testing the 14.3 canary it says it requires bumping React to 19 (which is still in beta? so assuming they are waiting until thats released) Maybe I'm missing something but why introduce a breaking change like that in a minor version?
@TALlama Thanks for letting me know about the typo! What that line you asked about is doing is reassigning the property to a proxified version of itself if it's not already. That will run exactly once, when the value is requested for the first time.
Unless you have experience teaching or training a variety of web tech (HTML, JS, CSS, SVG, etc), you likely don't fully understand their relative learning difficulty
Basing your assessment of which is harder on your attempts to teach yourself is esp unreliable
It's hard for you to know if a tech is hard or if you were just unlucky in stumbling into a bad entry point. Getting into something with the wrong mental model means you have to first unlearn a bunch of crap before you can actually learn