DEV Community

Cover image for Deploy Node API (Express Typescript) on Vercel
Tirth Patel
Tirth Patel

Posted on

Deploy Node API (Express Typescript) on Vercel

A couple of weeks back, I developed an API in Node based on Typescript. I tried to deploy it on Heroku.

But the process was long and time-consuming. Also, I noticed that Heroku is terminating free accounts from 28 Nov'22. ☚ī¸

Heroku

So I tried to experiment with various other platforms to deploy my Typescript-based Node API. Amon them free, robust, and versatile platform I found is VERCEL. Based on my experience, here are a few simple steps which you can follow and easily deploy Typescript-based Node API on Vercel. 🚀


1) Express + Typescript Boilerplate App ✏ī¸

Create express project with typescript. You can follow the below-mentioned steps to make a boilerplate for the project. (Github repo link is provided at end of article)

  • Initialize node project


    npm init -y
    
  • Install packages (you can use npm/yarn/pnpm)


    yarn add express
    yarn add -D typescript
    yarn add -D @types/node
    yarn add -D @types/express
    yarn add -D nodemon
    yarn add -D ts-node
    
  • Create tsconfig.json
    To work with typescript we need to make tsconfig.json file which will help to compile and build Typescript files in plain JS. Execute below command


    npx tsc --init --rootDir src --outDir build --esModuleInterop --resolveJsonModule --lib es6 --module commonjs --allowJs true --noImplicitAny true
    



Once the file is created you can keep it as is, or cleanup non necessary stuff. Replace content of tsconfig.json with following :


    {
    "compilerOptions": {
        "module": "commonjs",
        "esModuleInterop": true,
        "allowSyntheticDefaultImports": true,
        "target": "es6",
        "noImplicitAny": true,
        "moduleResolution": "node",
        "sourceMap": true,
        "outDir": "dist",
        "baseUrl": ".",
        "paths": {
            "*": ["node_modules/*", "src/types/*"]
        }
    },
    "include": ["./src/**/*"]
    }
Enter fullscreen mode Exit fullscreen mode
  • Update scripts in package.json


    "start": "nodemon src/index.ts",
    
  • Write express server code : Create file : src/index.ts and paste following code in it
  import express, { Request, Response } from 'express'

  const app = express()
  const port = process.env.PORT || 8080

  app.get('/', (_req: Request, res: Response) => {
    return res.send('Express Typescript on Vercel')
  })

  app.get('/ping', (_req: Request, res: Response) => {
    return res.send('pong 🏓')
  })

  app.listen(port, () => {
    return console.log(`Server is listening on ${port}`)
  })
Enter fullscreen mode Exit fullscreen mode
  • Spin up server : Run yarn start or npm run start command in terminal to start express serve. You can open browser and go to localhost:8080. API will return response of Express Typescript on Vercel.

2) Initialize git in our project. đŸ“Ĩ

  • Make a .gitignore file in the root of the folder. And add node_modules to it. If .gitignore file exists check that node_modules is added into it.
  • Execute git init in the terminal (from root of project) or you can use VS Code's source control tab to initialize git repository.
  • Connect local repo to remote (github/bitbucket). You can use any of the version control system to publish your repository.

3) Create Vercel project 🗃ī¸

  • Go to vercel.com -> Login
  • Login using the Version control platform you have kept your repository.
  • From the dashboard -> Add new project -> Select your repository -> Deploy

  • Afer deployment you will see something similar to this! 😟

Vercel Error
(ERROR 🚨)

  • Don't worry... Just follow on steps to fix it. 👍

4) Add Vercel config in app ⚙ī¸

  • In the above step, after your fist deploy is completed, you can see that we're not getting Express Typescript on Vercel response from API.
  • To work this as expected, we need to tell Vercel that is a API and you need to serve this as a serverless function.
  • For this, simply we need to add vercel.json file in root of our project. Paste below code in file.
{
    "version": 2,
    "builds": [
        {
            "src": "dist/index.js",
            "use": "@vercel/node",
            "config": { "includeFiles": ["dist/**"] }
        }
    ],
    "routes": [
        {
            "src": "/(.*)",
            "dest": "dist/index.js"
        }
    ]
}
Enter fullscreen mode Exit fullscreen mode



NOTE: Check your tsconfig.json file. The value against outDir must be kept instead of dist. If your config file has any other value than dist, replace it at either of both places.


5) Add a pre-commit hook 🏷ī¸

  • Vercel requires plain JS source files instead of Typescript. In order to do this, we need to build the project before committing and send compiled JS files so that Vercel can parse those files and serve the API.

  • Install pre-commit and rimraf package :


  yarn add -D pre-commit
  yarn add -D rimraf
Enter fullscreen mode Exit fullscreen mode
  • Modify scripts field in package.json file as follows:
  "scripts": {
  "start": "nodemon src/index.ts",
  "build": "rimraf dist && tsc",
  "ts.check": "tsc --project tsconfig.json",
  "add-build": "git add dist",
  "test": "echo \"Error: no test specified\" && exit 1"
  },
Enter fullscreen mode Exit fullscreen mode
  • Add new field pre-commit field in package.json :
  "pre-commit": [
      "ts.check",
      "build",
      "add-build"
  ]
Enter fullscreen mode Exit fullscreen mode
  • What this will do? → Whenever you will commit, the commands written in pre-commit will be executed. It will check Typescript errors, build the project and add build folder to the staged changes. (If you opt for manual build, don't forget to run build command to start build.)

5) Re-Deploy and Re-Check API 🔁

  • Commit the changes you have made and push the commit to GitHub. Check on vercel for the new deployment. Vercel will automatically trigger a new deployment on every push. Incase it is not started, you can manually start a deployment.

  • Once new deployment is live, you can copy the deploy URL and run in browser. You will see Express Typescript on Vercel as a API response. Hurrah 😃

API working

  • To assure that API is working perfectly, you can also hit /ping route which will return pong 🏓 as the response.

Ping Pong response

Closing comments 🙋‍♂ī¸

  • Thank you for following steps with me. Incase you find any issue in above mentioned steps, please ping in comment.
  • Also a humble request you to write which topic you want in my next blog. I will include that in my target list. đŸŽ¯
  • Github repo link for this project : Express Typescript Code



Tirth Patel, signing off! đŸĢĄ

Top comments (32)

Collapse
 
cel2022_01 profile image
Cel2022

It was useful but what I don´t undestand is why do we need to create dist directory?
That directory must be created when commit occurs but only into vercel.

  • Could you please explain that?
  • Have you tried to do the same but without the pre-commit dist folder creation?

How do I change the output directory in vercel.json #5081

Collapse
 
tirthpatel profile image
Tirth Patel

Hi @cel2022_01,
Good question. Actually the way VERCEL works is based on plain Javascript files. It can't directly operate on Typescript code. So inorder to run our Typescript based Express App, firstly we compile TS to JS. That compiled js source files are stored in dist folder. The path for dist folder is given in vercel config. So when any endpoint is hit to the server, VERCEL find the respective route in the dist folder and processes the request accordingly.

Hope this might resolve your query. Please continue the thread if more discussion is needed.
Thanks.

Collapse
 
thanhtutzaw profile image
ThanHtutZaw

We understand that but why can't vercel build and create the dist itself . Why dist need to be in git after git push .

Thread Thread
 
thanhtutzaw profile image
ThanHtutZaw

Deploying Nest and nextjs doesn't need to include dist folder in git source code .

Collapse
 
aliffazmi profile image
Aliff Azmi • Edited

Thanks!

This is very helpful.

For those who's still stuck at 404 error code missing in Vercel. Just remove the ignore built ts files which is in your .gitignore file. In this case remove or comment out the dist directory.

Image description

Collapse
 
tirthpatel profile image
Tirth Patel

Good catch @aliffazmi. Thank you for pointing it out. 👍

Collapse
 
fatemesoleymanian profile image
fatemesoleymanian

it helped me a lot! thank you

Collapse
 
mannu profile image
Mannu

Welcome to DEV community @fatemesoleymanian

Collapse
 
soozav profile image
Luis Verteliz • Edited

Hi Tirth, I'v tried to follow your instructions but I can make my app work, I get the following error: "Due to builds existing in your configuration file, the Build and Development Settings defined in your Project Settings will not apply."

In my app url I get the following error: "This Serverless Function has crashed".

Would you take a look at my code please?
github.com/SoozaV/sinecta-maps-bac...

Regards!

Collapse
 
soozav profile image
Luis Verteliz

I think I found out the issue looking at my function logs:

Image description

Do you have any idea on how to solve this? I can't find a solution.

Regards.

Collapse
 
tirthpatel profile image
Tirth Patel

Or you can do one more thing, in the vercel project setting page you can override the build command. You can try this one: npm i -g pg && npm run vercel-build

This will first install pg package in your VM on cloud server. Then you can access it while calling API. Please try this as well. And let me know if it works.

Cheers :)

Thread Thread
 
ashcript profile image
As Manjaka Josvah

I've tried it, but it seems like the error persists... Normally it should work, but I don't know why it doesn't... 😭

Thread Thread
 
ashcript profile image
As Manjaka Josvah

Image description

Thread Thread
 
ashcript profile image
As Manjaka Josvah

Finally, I've resolved it, not by installing pg globally with npm, but by adding the dialectModule option into my database configuration as below :

export const dbConfig = {
  username: process.env.DB_USERNAME,
  password: process.env.DB_PASSWORD,
  database: process.env.DB_NAME,
  host: process.env.DB_HOSTNAME,
  port: process.env.DB_PORT,
  dialect: 'postgres',
  dialectModule: pg, // I've added this.
  timezone: 'Etc/GMT+3', // Because process.env.TZ generated an error maybe due to time format
  define: {
    charset: 'utf8mb4',
    collate: 'utf8mb4_general_ci',
  },
  logging: false,
};
Enter fullscreen mode Exit fullscreen mode
Thread Thread
 
scherpablo profile image
Pablo Scherpa

Hello, I have the same problem, I put the dialectModule: pg in the DB conifg and nothing, still with the error. I have the DB in supabase and in vercel I installed the integration with supabase to see if it would be corrected but it didn't either. I don't know what to do anymore, is there any other alternative? Thank you.

Collapse
 
tirthpatel profile image
Tirth Patel

Hi @soozav It seems there is some issue with pg package. I've found one resource that might help you. Please check this PG package issue

Collapse
 
shimont profile image
Shimon Tolts

This tutorial helped me, thank you

Collapse
 
lucasvtiradentes profile image
Lucas Vieira

very useful thank you!

Collapse
 
pouriarezaeii profile image
Pouria Rezaei

Many thanks Tirth. I was stuck for 4 hours. Finally I found your post and Bingo!

Collapse
 
soydiego profile image
Diego Franchina

Hi, I hope you can help me.
I follow the tutorial and a lot of tutorials more and I couldn't get the solution.
Always I receive the same error on vercel: 404 not found.

I wrote a post in StackOverflow, maybe someone can reply or if you know what i'm doing wrong, i will appreaciate. This is the post of my question: stackoverflow.com/questions/775091...

Thanks for your time

Collapse
 
zhouzhonghao profile image
Bobby Zhou

Please refer to this question stackoverflow.com/questions/765767....
I posted an anwser there.

Collapse
 
zhouzhonghao profile image
Bobby Zhou

You need to share a demo so that another person can help you.

Collapse
 
soydiego profile image
Diego Franchina

Thanks. I didn't share a demo because I wrote my structure and my config file. with exactly all the things.

Collapse
 
pedrohvfernandes profile image
Pedro Henrique Vieira Fernandes • Edited

Hello, I did as taught in the post, but the build is not done at the time of commit, I use github desktop to make the commits.
Image description

Collapse
 
pedrohvfernandes profile image
Pedro Henrique Vieira Fernandes

The solution until then is to build manually

Collapse
 
uzzadev profile image
uzzadev

Hi Tirth!!
Today I was following your post, it's perfect and help me a lot, also is working very well, however I have a question/scenario...

Once that I deployed successfully but then I tried to add a config package from npm (npmjs.com/package/config), which I used to manage different environment variables (development, production for instance),
and then I deploy to Vercel, I get the same 404 NOT_FOUND error.

Since the npm config package require to add a folder in root project called "config" where can include the environments configurations files for each environment, I thinking the problem is something missing in vercel.json config file in order to include the compiled config ts files.

I would appreciate if you can help me with some clues about this error or help me to understand and fix it.

Regards!

Collapse
 
tirthpatel profile image
Tirth Patel

Hi @uzzadev ,
I'm happy to hear that many developers like you are following the blog and it is helping to resolve your issue.

For the error you are facing is because there is some mis configuration in the VERCEL config. In the tsconfig.json file we're putting which files to include. Please check those parameters as well. Generally we include src folder and its subfolders. If you need to include any files/folders which are in root of the project, then please modify the tsconfig.json file.

Once you have configured the parameter, run the yarn build command. And in the dist folder, check whether the files which you included are having any presence/reference or not.

So the thumb rule is, VERCEL will pick all which it will get in dist folder. If any file/configuration is missing the server will throw 404/500 error.

Hope this might help you out to further debug the issue.
Thanks :)

Collapse
 
musharaffleapo profile image
musharaf-fleapo

Really Helpful thanks

Collapse
 
glauberdm profile image
Glauber Duarte Monteiro

Thank you very much!

Collapse
 
cakrads profile image
Cakra Danu Sedayu

thank you so much, this really helpful..

Is there a way to avoid pushing the dist folder?
So Vercel will build and generate the dist folder for us

Collapse
 
ochukodotspace profile image
Ochuko

Thank you, this helped a lot!

Collapse
 
samukbg profile image
Samuel Bezerra Gomes

Super useful! Thanks mate