Closed sean-s14 closed 1 year ago
same
Should be fixable by adding __NEXT_PRIVATE_PREBUNDLED_REACT
to your .env file as mentioned in the only other, pinned and duplicate issue for this repo: #4.
I'm hesitant to add a hack for it in this repo since the monkey-patch react-dom situation is frankly a bit of a mess on NextJS-side. Hopefully they'll get this sorted, since this is causing issues all over the ecosystem, (except for Vercel hosted NextJS, conveniently)
next: 13.4.7 next-dev-https: 0.13.3
Running script
next-dev-https --https --port 4430
generates the following error: