Did the recent Next.js Conference get you excited for the future? See how easy it is with Vercel to deploy a working app in minutes. Deploying Next.js 10 with Vercel CLI and the Vercel GitHub Integration
Back in the day when Vercel was Zeit and the Vercel CLI was simply
now, I was blown away by the simplicity of it all. You could, at the time, deploy contains and I made that count during that golden Bitcoin phase of 2018 (yep, what a throwback).
After the recent Next.js Conference and announcement of Next.js 10, I have been very tempted to make some changes to how I deploy my applications.
I am still working through it, but as it currently stands, I am not into the idea of fighting against the grain to get Lambda functions working with Next.js 9+ (yes, there is a serverless plugin but it doesn’t suit the workflow I was going for).
So, I have decided to jump back into Vercel and see what is fresh and put some focus on Next.js.
Today’s post will be about simply reliving the making deployments with Vercel.
The requirements are that you have a Vercel and GitHub account.
We need to run some groundwork. From a project base, let’s use create-next-app to create a Next.js 10 app that we will deploy with the Vercel CLI that we will install.
Once we install and create our basic scaffold, we will need to log into our Vercel account using
This will prompt you for an email address. Once this has been entered, head to your email to verify the code.
This will log you in from the CLI and you are ready to go!
Now, here is the magic… just run
Follow the prompts for the scope and project you are happy enough to deploy.
The prompts will give you a URL to inspect so you can see the progress of the deployment.
Article covers: How native is react native?, React Native vs (Ionic, Cordova), Similarities and difference between React Native and Native App Development.
Swiftly deploy your static websites with Vercel
I have been using React JS in my projects for quite some time now and am used to managing routing in my app using the react-router package. I have always been keen on having as little dependencies in my apps as possible, so, I always felt perturbed by the use of this particular package in simpler apps which did not have complex routes.