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.
With our GitHub and GitLab integrations, we enabled deploying on every git push, 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.
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 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).
Note: Using Next.js with next dev will run both your front-end and serverless functions already. You do not need to use vercel dev.
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 see vercel dev improve: Which technologies, platforms, and frameworks you would like us to support, or any hiccups or slow paths you run into.
Furthermore, we also set up a FAQ page containing several common questions that might come up when using vercel dev and their answers.