Still no option to export a static site when using next/image without relying on 3rd party services, right?<p>The only option that comes to my mind is using Vercel to host the site but then every image is transformed on demand which results in horrendous loading times.<p>Is this really how „everyone“ uses Next when exporting static sites?
Partial hydration would have been a game changer in performance of nextJS based websites.<p>I am a bit perplexed about the new "live" feature. Its just so far away from the framework business (poof, now its an IDE), I have no words for it...
Great to see reduced cumulative layout shift in image tags! Next.js seems to be the only modern JS framework with accessibility by default. Still wishing i18n would work with `next export`, though.
I see Next.js being pushed into areas where is shouldn't be used. And I mean like data heavy enterprise web apps. Probably in a year or two these projects will collapse under the heavy maintenance burden and will start seeing a lot of unearned negativity towards Next.JS
For the interested they are having a conference right now [1].<p>1: <a href="https://www.youtube.com/watch?v=ze8ycxc1UzE" rel="nofollow">https://www.youtube.com/watch?v=ze8ycxc1UzE</a>
Really solid release, congrats to the team and contributors!<p>P.S. I have noticed that you put a markdown link as `src` prop value in the first `Script` example.
Related ongoing thread:<p><i>Next.js Live: Code in the Browser with ESM, ServiceWorkers, Replicache, and WASM</i> - <a href="https://news.ycombinator.com/item?id=27517440" rel="nofollow">https://news.ycombinator.com/item?id=27517440</a> - June 2021 (23 comments)
> Since Next.js 10, we've been obsessed with further improving the developer experience of Next.js. In 10.1 and 10.2 we improved startup time by up to 24% and shaved off another 40% of processing time for changes through React Fast Refresh. You've been getting these amazing speed improvements just by keeping Next.js updated.<p>I know they think this is good marketing, but it absolutely does not inspire confidence. Why was it so slow to begin with? Why would someone who’s never used Next.js want to use it after reading this?<p>Too many JavaScript projects talk about how much faster they’re getting or how “blazing” fast they are. I don’t think these people know what “fast” is.