TLDR; in this article, I claim it's best for folks who know React to start with Next.js from the beginning. We also get into why it would be a soun...
For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Too long, didnt read lol
I left you a TLDR at the very top 🙂
On one of the more recent projects we worked on we tried to make a NextJS app but we ran into a huge roadblock with deployment. Simply put, if you're starting from nothing, there doesn't seem to be anything out there that explains how you might deploy a NextJS app on AWS or Google Cloud, etc. And putting my cynical hat on, I ended up pointing at ZEIT Now as the reason.
Super fair point about the documentation lacking in that area. At my day job, we run Next apps in K8s hosted on AWS pretty easily.
Nader Dabit did a great write up on how to deploy to AWS using Amplify.
dev.to/dabit3/5-minute-tutorial-de...
For the folks reading this wondering "how can I measure performance in Next apps?" check out this new article I just wrote about Web Vitals:
dev.to/dbredvick/intro-to-core-web...
Amazing article!!
Thanks really amazing article
Great article, thanks! What kind of projects would you advice not to use Next.js?
Summary:
Why React? Because it's popular
Why next? Because you want slow SSR
SSR isn't really the only option for Next.js apps anymore. Have you looked into
getIntialProps,getStaticPaths, and Incremental Static Regeneration? All forms of SSG and that super fast.Why React isn't really the correct subtitle for that area of the essay. It's important to know that Next.js likely only became popular by riding the wave of React.
There are much better resources than this essay that talk about why React is a solid technical choice.
Next 12. Using RUST over we pack, SPEEEED
Hi, I was wondering. Could you configure next/font to Babel on your project manually. Or could you change the default don't from next/font to something else manually?