Jobs not showing up using latest 6.7.1 with Nest.js

[pboutin]

After updating our app with Nest.js v11 and the latest version of bull-board, the jobs don't show up anymore. We only see the counts.

Our versions

"@bull-board/api": "^6.7.1",
"@bull-board/express": "^6.7.1",
"@bull-board/nestjs": "^6.7.1",

Checking the network tab for the API response shows jobs: [].

Screenshot of the board

[felixmosh]

Probably related to something that changed in that major version...
The missing part is the query param of queue name, can you debug it?

[Chelovekk]

Yeah somewhere inside express adapter query are lost (present in middlewares added right before router). Maybe its related to updates of express req.query.

https://expressjs.com/en/guide/migrating-5.html#req.query

[pboutin]

Enabling the extended query parser doesn't resolve the issue.

https://docs.nestjs.com/migration-guide#query-parameters-parsing

EDIT:
In an express middleware, I can log the query params and the activeQueue is there.

  app.use((request: Request, response: Response, next: NextFunction) => {
    console.log(request.path, request.query);
    ...

Logs:

/queues/api/queues {
  activeQueue: 'synchronize_activity',
  status: 'completed',
  page: '1',
  jobsPerPage: '10'
}

[fstn]

It was working yesterday, I just update my dependencies and I have now the same issue, jobs not showing.
Nothing changed in the code execept that

[fullstackjedi]

Yeah I have same issue as well, most likely related to nestjs 11 uses express 5

[felixmosh]

Someone can create a small repo that replicates this issue?

[jsfrocha]

@pboutin I know this may sound strange, believe me, I spent hours trying to debug this. I set up a minimal repo and the issue was not there. I'm using Nest Workspaces so I thought it was something related to that.

The only difference between my repo and the minimal repo was the package manager - NPM on the minimal and Yarn on the bugged one.

From what I could see (by adding logs on @bull-board/express), the bugged repo was still using Express v4 on ExpressAdapter - when I replaced Yarn for NPM, it started using the correct Express version and the issue was fixed.

Also, make sure to add "express": "^5.0.1", to the dependencies of the project directly.

[felixmosh]

@jsfrocha we do have express 5 as an optional dep

[dmitriy-kudelko]

Also, make sure to add "express": "^5.0.1", to the dependencies of the project directly.

This doesn't seem to help as "express": "^4.21.1 || ^5.0.0" specified in the bull board's package.json resolves to 4.21.1:

> npm ls express 

├─┬ @bull-board/express@6.7.7
│ └── express@4.21.2
├─┬ @nestjs/platform-express@11.0.8
│ └── express@5.0.1 deduped
├── express@5.0.1
└─┬ swagger-ui-express@5.0.1
  └── express@5.0.1 deduped

The only thing which helps so far is overriding the express version in the resolutions field of package.json (we're using pnpm). I assume the same should work for yarn with the overrides field.

[pboutin]

Explicitly installing express v5 fixes my issue 👍

[matt-lookatme]

Ended up with this solution for pnpm to force @bull-board/express to have the right express version

  "pnpm": {
    "overrides": {
      "@bull-board/express>express": "5.0.1"
    }
  }

https://pnpm.io/package_json#pnpmoverrides

[webdev51]

I also had the same problem fixed it by doing something similar as matt-lookatme . I added below to my package.json and re-run yarn:

  "resolutions": {
    "@bull-board/express/express": "5.0.1"
  },

[aimon7]

Ended up with this solution for pnpm to force @bull-board/express to have the right express version

"pnpm": {
"overrides": {
"@bull-board/express>express": "5.0.1"
}
}

https://pnpm.io/package_json#pnpmoverrides

Thank you 🙏

[KRaymundus]

I read that is due to the res.req / res.res compatibility issue with Express 5-style responses in newer NestJS versions.

Since we're using npm, the syntax for the package.json is:

"dependencies": {
  ...
},
"devDependencies": {
  ...
},
"overrides": {
  "@bull-board/express": {
    "express": "5.0.1"
  }
},

Then run npm install