With Next.js and Vercel, creating and deploying production-ready web apps has never been easier. It is optimized for running high-performance production workloads and provides a world-class developer experience straight out of the box. Continue reading to learn more about what makes Next.js so appealing to work with and how simple it is to publish your code to production.<\/p>\n\n\n\n
Ensure that “npm” is installed on your computer:<\/p>\n\n\n\n
node -v && npm -v<\/code><\/pre>\n\n\n\nThe corresponding version numbers should be printed to the console. If not, you can find installation instructions for your platform from the official Node.js<\/a> site.<\/p>\n\n\n\nWe can use the following command to scaffold out a new Next.js project if we have the node toolchain installed on our machines:<\/p>\n\n\n\n
npx create-next-app my-amazing-app<\/code><\/pre>\n\n\n\nStart the development server by going to the directory you just created:<\/p>\n\n\n\n
cd my-amazing-app && npm run dev<\/code><\/pre>\n\n\n\nBy default, your app will be served at localhost:3000<\/a>, and when you visit it with your browser, you’ll be greeted with the default welcome screen.<\/p>\n\n\n\nStatic Data Fetching<\/h2>\n\n\n\n
The “getStaticProps” data-fetching hook allows you to provide dynamic data to your pages at build time. This is ideal for marketing pages when data isn’t updated frequently and speed is a top consideration. Replace the default contents of “pages\/index.js” with the following code:<\/p>\n\n\n\n
import Head from \"next\/head\";\n\nexport default function Home({\n title = \"Hello World!\",\n metaContent = \"Generic SEO pitch\",\n copy = \"I'm having writer's block.\",\n}) {\n return (\n <>\n <Head>\n <title>{title}<\/title>\n <meta content={metaContent} \/>\n <\/Head>\n <div>\n <h1>{title}<\/h1>\n <p>{copy}<\/p>\n <\/div>\n <\/>\n );\n}\n\nexport const getStaticProps = async () => {\n \/\/ This is a full server-side Node environment,\n \/\/ which means that you can make network requests,\n \/\/ talk to databases, read from the file-system,\n \/\/ and do whatever you want to fetch your data.\n\n return {\n props: {\n title: \"My Amazing Startup\",\n metaContent: \"Amazing SEO poetry\",\n copy:\n \"I'm in the business of making people smile. That's all I'm here for.\",\n },\n };\n};<\/code><\/pre>\n\n\n\nEverything is the same as it is in any other React project, with a few exceptions. First, you’ll see that we’re not explicitly importing React because Next.js includes it by default. Next, you can see that we’re able to set our page metadata from the\u00a0“<Head \/><\/code>”\u00a0component and don’t need to bring in another third-party library like react-helmet<\/a>. Finally, we’ve included a “getStaticProps” function that returns a props object with the title, “metaContent”, and “copy” keys. As a result, we can de-structure those props from our top-level page component and read them in. For good measure, we’ve included default values in case the props aren’t supplied. These props are baked immediately into your pages with no runtime overhead when your Next.js project is constructed, resulting in enhanced performance and stability.<\/p>\n\n\n\nIncremental Static Regeneration<\/h2>\n\n\n\n
Next. The distinction between static and dynamic is blurred by JavaScript. Just because your data is statically fetched doesn’t imply you’ll be stuck with it until you re-deploy. Incremental Static Regeneration allows you to refresh existing pages as traffic comes in by re-rendering them in the background. Simply append the “revalidate” key to the object returned by the “getStaticProps” function, along with the number of seconds you want to wait before revalidating and recreating the page if data changes. You might not notice a change in our somewhat contrived local example, but it will come to life once you start accessing data from a database or CMS.<\/p>\n\n\n\n
export const getStaticProps = async () => {\n return {\n props: {\n title: \"My Amazing Startup\",\n copy:\n \"I'm in the business of making people smile. That's all I'm here for.\",\n },\n revalidate: 1, \/\/ number of seconds to wait before revalidating\n };\n};<\/code><\/pre>\n\n\n\nServer Side Rendering<\/h2>\n\n\n\n
You may have very dynamic material that needs to update based on a variety of factors. Perhaps you’d like to look at the request headers of incoming traffic to see how you want to render your page. Next.js provides the “getServerSideProps” function for this purpose, which is similar to the “getStaticProps” function we’ve already seen.<\/p>\n\n\n\n
Create a new file in your “pages” directory called “hello-user-agent.js” with the following contents:<\/p>\n\n\n\n
import Head from \"next\/head\";\n\nexport default function HelloUserAgent({ userAgent = \"Nobody\" }) {\n return (\n <>\n <Head>\n <title>Hello User Agent!<\/title>\n <\/Head>\n <p>\n {\" \"}\n Hi <em>{userAgent}<\/em> !{\" \"}\n <\/p>\n <\/>\n );\n}\n\nexport const getServerSideProps = async ({ req }) => {\n return {\n props: {\n userAgent: req.headers[\"user-agent\"],\n },\n };\n};<\/code><\/pre>\n\n\n\nThis page has a structure identical to our “index.js” home page, but with one minor modification. We are exposing a function named “getServerSideProps” instead of a “getStaticProps” function below our page component. Notice how we’ve destructed a Node.js HTTP Incoming Message<\/a> object and read values from it in the body of our function. This page is totally rendered in a server environment using a lightweight Serverless Function<\/a>, which gives your page new props every time it’s requested. You’ll see your browser’s user agent string printed on the screen if you go to “localhost:3000\/hello-user-agent”.<\/p>\n\n\n\nIt’s worth noting that rendering a page in this manner has a tiny performance penalty. It can take a few moments (500-800 ms on average) for the function that renders your page to start up if it hasn’t been used in a few minutes. The cold start<\/a> problem is what this is known as. This difficulty can be mitigated with a good caching approach<\/a>.<\/p>\n\n\n\nAPI Routes<\/h2>\n\n\n\n
API Routes let you design HTTP request handlers with the same file-system routing structure as the frontend. When we used “create-next-app” to create our project, an API route was built for us at “pages\/api\/hello.js” with the following contents:<\/p>\n\n\n\n
export default (req, res) => {\n res.statusCode = 200\n res.json({ name: 'John Doe' })\n}<\/code><\/pre>\n\n\n\nThe function will produce a JSON response if you browse to localhost:3000\/api\/hello<\/a>. API Routes are useful for connecting to a database rapidly and delivering results, as well as processing forms and sending emails.<\/p>\n\n\n\nDeploy to Vercel<\/h2>\n\n\n\n
Now that we’ve got a feel for how Next.js works, we need a way to get it up on the internet. Vercel is a deployment platform for frontend projects made by the same people that created Next.js, so its only natural that the deployment experience feels as simple as the development experience.<\/p>\n\n\n\n
Create a new git repository and push it to a Git provider to get started. After you’ve created a URL for your repository, go to https:\/\/deploy.new\/<\/a> to begin the import process. A new account will be created for you if you don’t already have one, and a deployment will be made to your account. It’s as simple as that! The Vercel Edge Network<\/a> distributes your Next.js project all over the world. Every time you push changes or create a new branch, your URL will be updated and a new deployment will be created for you. The Vercel platform’s documentation<\/a> might help you learn more about it.<\/p>\n\n\n\nAlthough the Git workflow is great for iterating on a production app, you may utilize the Vercel CLI<\/a> to make a deployment by running the “vercel” command from your project root.<\/p>\n\n\n\nFinal Thoughts<\/h2>\n\n\n\n
Next.js is a robust framework for projects of any size, although it hides a lot of the finer points and emphasizes minimalism. It has a hybrid rendering strategy that allows you to choose whether you want static markup with pre-populated props supplied at build time or server-rendered pages with dynamic data requirements for each request on a per-page basis. API routes make it easier to set up a backend without having to use Express or other API frameworks. We’ve gone through the most important aspects of Next.js, but we’ve only scratched the surface. To learn more, see the official documents<\/a> and check out the interactive learning tutorial<\/a> for creating your own blog from the ground up!<\/p>\n","protected":false},"excerpt":{"rendered":"With Next.js and Vercel, creating and deploying production-ready web apps has never been easier. It is optimized for running high-performance production workloads and provides a world-class developer experience straight out of the box. Continue reading to learn more about what makes Next.js so appealing to work with and how simple it is to publish your […]<\/p>\n","protected":false},"author":2,"featured_media":6375,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[145,77,62],"tags":[146,73,110],"jetpack_featured_media_url":"https:\/\/azoora.com\/blog\/wp-content\/uploads\/2021\/08\/easily-deloy-a-next.js-app-with-vercel.png","jetpack_publicize_connections":[],"jetpack_shortlink":"https:\/\/wp.me\/p7FQPL-1EO","jetpack-related-posts":[],"jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts\/6374"}],"collection":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/comments?post=6374"}],"version-history":[{"count":1,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts\/6374\/revisions"}],"predecessor-version":[{"id":6376,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts\/6374\/revisions\/6376"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/media\/6375"}],"wp:attachment":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/media?parent=6374"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/categories?post=6374"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/tags?post=6374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}