Skip to content

SignalR JavaScript client changing package name to @microsoft/signalr #14906

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

Closed
Tratcher opened this issue Oct 2, 2019 · 0 comments · Fixed by #15044
Closed

SignalR JavaScript client changing package name to @microsoft/signalr #14906

Tratcher opened this issue Oct 2, 2019 · 0 comments · Fixed by #15044
Assignees
Labels
breaking-change Indicates a .NET Core breaking change

Comments

@Tratcher
Copy link
Member

Tratcher commented Oct 2, 2019

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

  • Issue type: breaking-change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants