Skip to content

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

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

Open
analogrelay opened this issue Jun 27, 2019 · 0 comments
Open
Labels
3.0.0 Announcements related to ASP.NET Core 3.0 Announcement Breaking change Documented The breaking change has been published to the .NET Core docs Migrated

Comments

@analogrelay
Copy link

analogrelay commented Jun 27, 2019

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.

[This announcement has been migrated to: dotnet/docs#14906]

@analogrelay analogrelay added Announcement Breaking change 3.0.0 Announcements related to ASP.NET Core 3.0 labels Jun 27, 2019
@aspnet aspnet locked and limited conversation to collaborators Jun 27, 2019
@analogrelay analogrelay added this to the 3.0.0-preview7 milestone Jun 27, 2019
@Tratcher Tratcher removed their assignment Oct 2, 2019
@scottaddie scottaddie added the Documented The breaking change has been published to the .NET Core docs label Dec 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3.0.0 Announcements related to ASP.NET Core 3.0 Announcement Breaking change Documented The breaking change has been published to the .NET Core docs Migrated
Projects
None yet
Development

No branches or pull requests

3 participants