Closed fdcastel closed 1 year ago
Is it just a type check? Did you test this package by @microsoft/signalr 7.0.10
?
i think if you want to work with new version we should update react-signalr
Is it just a type check?
To the best of my understanding, yes.
Did you test this package by
@microsoft/signalr 7.0.10
?
Exactly.
It's the latest version installed when you do not specify any constraints (npm i @microsoft/signalr
)
New users of react-signalr
(like me 😉) will have the same problem.
fixed: v0.2.18
When using
@microsoft/signalr 7.0.10
I'm getting this error on build.Reverting to
@microsoft/signalr 6.0.21
the problem doesn't occur.