-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TS2322: Type 'BullMQAdapter' is not assignable to type 'BaseAdapter' (Wrong Types) #271
Comments
After some investigation I have checked that the problem was created by the following string I removed If so, a pull request #272 in opened. But I am not sure, that fixing my problem won't cause any others. |
Thank you @AlexZeDim ... But seems that your fix failing on CI. Try to remove @types/bull-board from your project since we ship the lib with built in types |
I have tried with and without it. As for now, I am using 2.0.2 (latest) For example And |
It is a confusion of types... not related to this lib. can you try a fresh install? (removing |
Already done it too with |
Thank you for reporting this issue, I was able to reproduce the issue update updating types to latest 🙏🏼 |
Fix released at |
can we fix this for those on v1.*? It is still present in 1.7.2 |
Why do you not updating to v2? The breaking changes are minor |
Hi!
I got almost the same issue, as it was mentioned a while ago in this report #253. Unless old things don't help me.
Node.js: 16.1
package.json
As you may see, I am using
bull-board
withnestjs
. Here is a code image with error description:Part of
tsconfig.json
responsible forimports
:And my
IORedis tree
What have I done:
Of course, I have tried various things, like declaring variables with queues outside the
createBullBoard
part, downgrading (which helps), and so on.But the funniest thing is, that actually
bull-board
is working fine, if I prefer to ignore errors manually via// @ts-ignore
comments. So it's problem with interfaces, not with workability. But it is challengings to use bull-board in production.The text was updated successfully, but these errors were encountered: