Hi @empara, welcome to the Vercel Community!

Sorry to see you are facing this issue.

Without looking at the whole repository it's tough to guide what might be going wrong. Although, I do have a suggestion to move away from the legacy APIs (builds and routes) from the Vercel configuration in favor of:

1
{
2
  "rewrites": [{ "source": "/(.*)", "destination": "/server" }]
3
}

Can you help me with some more information:

• What is the folder structure for your project?
• How do you run the project locally?

Hello @anshumanb, thank you for your reply :)

To start the api locally, I just do npm i (if needed) and npm start

The architecture looks like this:

The api start with server.js which then calls the other files, the principal code is in the src folder, Controllers and models contains the functions that will call the db. The folder and file : helm, cloudbuild.yaml and Dockerfile are useless in this case (they were used when we deployed the project on gcloud)

I'm not sure what information exactly you need, so feel free to ask anything

Hi @empara, thanks for sharing this information. I see that you were previously deploying your application with Docker and gcloud, which is a server environment. Vercel on the other hand is serverless. So, it could be that some parts of the server.js are not exactly in the format that Vercel expects.

I'd recommend giving https://vercel.com/guides/using-express-with-vercel a read.

If you could share what the project comprises of (frontend, backend, queues etc) that'd be helpful. Also, what does the npm start do, is it just node server.js?

Hello,

Yes indeed vercel is serverless, but it still worked with other projects that were in a server environment, and they all use express including this one.

The npm start just does "node server.js" And the code is as follows:

1
const express = require("express")
2
const http = require("http")
3

4
const app = express()
5
const server = http.createServer(app)
6
server.listen(1100, () => console.log(`Listening on port 1100`))

And the project comprises of queues.

I was thinking maybe the problem comes from this part:

1
const { ExpressAdapter } = require("@bull-board/express")
2
const { createBullBoard } = require("@bull-board/api")
3
const { BullAdapter } = require("@bull-board/api/bullAdapter")
4
const serverAdapter = new ExpressAdapter()
5

6
serverAdapter.setBasePath("/admin/queues")
7
const { addQueue, removeQueue, setQueues, replaceQueues } = createBullBoard({
8
	queues: [new BullAdapter(stripeQueue)],
9
	serverAdapter: serverAdapter,
10
})

But I don't see why this would block the dependency @bull-board/ui to be installed

Hi @empara, thanks for the information. I think I found the culprit.

There's an open issue on the bull-board repository but one of the comment got it working on Vercel. So can you try this solution:

https://github.com/felixmosh/bull-board/issues/444#issuecomment-1944329328

GitHub

Next.js & Vercel Support · Issue #444 · felixmosh/bull-board

There's an ongoing thread #124 here about how to integrate bull-board/express with Nextjs. The latest solution works great, however, if you are deploying to Vercel you run into issues trying to acc...

I hope this helps. Please do share the outcome here.

Hello,

Sorry for the late reply (was on vacation) I tried the solution on the topic you've sent me and it seemed to work but I had different errors. After pulling out my hair, I completely removed bull and other stuff that was on the api but it still didn't work, and finally after doing some random testing and with the help of chatgpt I figured out what was the problem:

1
const server = http.createServer(app)

I just had to remove this and it magically worked, I have no experience with serverless but it looks like vercel doesn't like the createServer function. It all works now, thank you for your help :)

Hi @empara, thank you so much for sharing back the solution in the community.