You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SignalR JavaScript client changing package name to @microsoft/signalr
In 3.0.0-preview7, the SignalR JavaScript client will change from being @aspnet/signalr to @microsoft/signalr. We are doing this to reflect the fact that SignalR is useful in more than just ASP.NET Core applications, thanks to the Azure SignalR Service.
To react to this change, you will need to change your references in package.json files, require statements, and ECMAScript import statements. No API will change as part of this rename.
SignalR JavaScript client changing package name to
@microsoft/signalr
In 3.0.0-preview7, the SignalR JavaScript client will change from being
@aspnet/signalr
to@microsoft/signalr
. We are doing this to reflect the fact that SignalR is useful in more than just ASP.NET Core applications, thanks to the Azure SignalR Service.To react to this change, you will need to change your references in package.json files, require statements, and ECMAScript import statements. No API will change as part of this rename.
Please use dotnet/aspnetcore#11637 for discussions on this change.
Version introduced
3.0
Old behavior
The client package was named
@aspnet/signalr
.New behavior
The client package is now named
@microsoft/signalr
.Reason for change
We are doing this to reflect the fact that SignalR is useful in more than just ASP.NET Core applications, thanks to the Azure SignalR Service.
Recommended action
Switch to the new package
@microsoft/signalr
.Category
ASP.NET Core
Affected APIs
Not detectable via API analysis
Issue metadata
The text was updated successfully, but these errors were encountered: