Vercel was born out of the idea that deploying a website could be much simpler. You only have to run a single command: vercel – that is all.

git push , and teams to manage staging and production by simply merging pull requests. With our GitHub and GitLab integrations, we enabled deploying on every, and teams to manage staging and production by simply merging pull requests.

Not only did Vercel make deployments effortless, it made them scalable and global by default. Thanks to monorepo support, you could develop static websites and serverless functions within the same repository.

Today, we are excited to announce one command to run it all on localhost: vercel dev .

Typically, developing a website or application involves a series of steps:

Cloning repositories

Fetching packages

Synchronizing and matching ports

Downloading the right runtime for each programming language

And so on...

Even for modern projects, we often need to look up the README.md file for instructions about installing dependencies, and then tell a package manager to run developer scripts.

Vercel gives you a different contract. It is always vercel dev .

When you work with servers, the developer workflow is quite tedious. You have to run a process, find the port, then make your changes, then kill the process (usually with Control+C)...

When you work with modern frontend frameworks (like Next.js or Gatsby) your HTML, CSS and client-side JavaScript, hot-reloading is expected instead.

When you introduce API endpoints written as serverless functions, we now also have the advantage of bringing live reloading to your backend. vercel dev ensures that every single request builds and runs the latest version of your code (yes, like .php for every language).

Every piece of technology, from the client to the Builders that compile your code into static files and lambda functions, is fully open-source and MIT licensed.

Vercel ensures that you write code with the same open and standard APIs of your programming language or framework of choice.

Whether it is Next.js pages, Node.js HTTP request handlers or Express.js endpoints – we ensure that your code remains agnostic and portable.

Unlike the next dev command, vercel dev allows you to run your entire suite of web apps and APIs all at once, with just a single command.

For example, the application shown below uses both a Next.js frontend and a Node.js API – both running at the same time using vercel dev :

No matter how many builds, `vercel dev` will boot them all.

dev script in package.json ... If you are building a static site using a tool like Gatsby , all you need to do is add the command you would normally use to ascript in...

{ "scripts" : { "dev" : "gatsby develop -p $PORT" } }

Once that is completed, the tool (in this case gatsby develop ) is invoked automatically.

The Gatsbygram example showcases this really well:

In this example, Gatsbygram is run using `vercel dev`.

vercel dev , you just run the command: If you chose to write a backend in Go , there are no changes to be made in order for your project to work with, you just run the command:

In this example, a static site and a Go serverless function are run in parallel.

vercel dev emulates production closely: Even if your application is spawning a instance of Headless Chrome (like puppeteer ), local development will be very smooth, asemulates production closely:

As you can see, both `vercel dev` and `puppeteer` will boot up in no time.

vercel dev also acts as a substitute for As a bonus, you will be glad to know thatalso acts as a substitute for serve out of the box. Any time you want to serve a directory quickly, you know what to reach for:

Even though there is no `vercel.json` file, serving the directory just works.

vercel dev is available in beta as part of the latest version of is available in beta as part of the latest version of Vercel CLI

If you need a quick project to test it with, try vercel init :

vercel init nextjs cd nextjs

and then...

vercel dev

vercel dev improve: Which technologies, platforms and frameworks you would like us to support, or any hiccups or slow paths you run into. We want to hear from you and have set up a dedicated feedback form to learn more about the different ways in which you would like to seeimprove: Which technologies, platforms and frameworks you would like us to support, or any hiccups or slow paths you run into.

vercel dev and their answers. Furthermore, we also set up a FAQ page containing several common questions that might come up when usingand their answers.