Deploying a Node.js app does not have to mean managing a server. Here is how to prepare your project, deploy from a zip or GitHub, set environment variables and fix failed builds.
Building a Node.js app is one thing; getting it online reliably is another. You do not always need to manage your own server. Many hosting plans now let you deploy a Node.js app from a zip file or a GitHub repository, build it automatically and run it for you. This guide shows how to prepare and deploy your project step by step.
Make sure package.json lists all dependencies (not just in your local node_modules), and has scripts like:
"scripts": {
"build": "next build",
"start": "next start"
}Specify the Node.js version your app needs, and commit your lock file (package-lock.json, yarn.lock or pnpm-lock.yaml).
A good hosting panel reads package.json and suggests settings. Check:
| Setting | Example |
|---|---|
| Framework | Next.js, Express, Vite |
| Node.js version | 20 or 22 |
| Build script | build |
| Output folder | .next, dist or build |
| Entry file (server apps) | server.js |
| Package manager | npm, yarn or pnpm |
Never put secrets in your code. Add variables like DATABASE_URL, API keys and JWT secrets in the hosting panel. Remember: some frameworks (like Next.js with NEXT_PUBLIC_ variables) read values at build time, so you must redeploy after changing them.
Start the deploy and follow the log. A typical log shows dependency installation, the build and the app starting. When it completes, open your domain and test the main pages and API routes.
Add the webhook address from your hosting panel to your repository settings. Every push to your main branch then rebuilds and deploys automatically – no manual uploads.
Some hosting plans now support Node.js apps with automatic builds, so you do not need a separate server. Check that your plan supports Node.js and the version your framework needs.
No. Leave node_modules out of the zip. The server installs dependencies from your package.json and lock file, which keeps uploads small and avoids compatibility problems.
Common reasons are missing environment variables, a dependency installed globally on your computer but not listed in package.json, a different Node.js version, or a hard-coded port instead of process.env.PORT.
To deploy a Node.js app, prepare a clean package.json, upload a zip or connect GitHub, review the detected build settings, add environment variables, follow the build log and automate future deploys with a webhook.
Our web hosting includes Node.js app deploys from a zip or GitHub/GitLab with live build logs, environment variables and push-to-deploy. Need a custom app built? See software development or contact us.
Spreadsheets and off-the-shelf apps work – until they do not. Here is how to decide between ready-made tools and custom software, and how to start small if you build.
Read article: Custom Software vs Ready-Made Tools: How to Choose for Your Business"This site can't be reached", a 500 error, a red privacy warning or a blank white page? Each message points to a different cause. Here is how to read it and get your website back online.
Read article: Website Not Opening? What Each Error Means and How to Fix It FastYour quotes, invoices and replies land in the customer's spam folder – or never arrive at all. Here is how to find the exact reason in 10 minutes and fix it for good.
Read article: Why Your Business Emails Are Going to Spam (and How to Fix It)
