[Discussion] SignalR JavaScript client changing package name to @microsoft/signalr

[analogrelay]

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.

This is the discussion issue for aspnet/Announcements#372.

[GeraudFabien]

Hello, I'm curious about what make you choose between:

1. Microsoft
2. dotnet
3. SignalR
4. A new one

I don't have any preference or idea on the subject i'm just curious.

[Mertsch]

The organization
https://github.com/SignalR
could probably also use a new description to reflect the change

SignalR
SignalR for ASP.NET

[analogrelay]

The organization
@SignalR
could probably also use a new description to reflect the change

Right now, the SignalR GitHub organization hosts ASP.NET SignalR (the version that predates this one). We are doing some work to consider how to restructure things like this though.

Hello, I'm curious about what make you choose between ...

We considered most of these:

1. @dotnet/signalr continues to indicate SignalR can only be used with .NET, which has the same problem as @aspnet/signalr. With the Azure SignalR Service REST APIs and Azure Functions bindings, it's now possible to write a SignalR app without a single line of C# (though C# is still a fantastic language to do so in!).

2. @signalr/client gives us a place to hang other things, and creates a new identity, but in general we've been leaning away from doing that and want to consolidate a bit around a few Microsoft identities (see https://github.com/Microsoft for example)

3. @azure/signalr would align it with a bunch of other Azure clients. However, this has the opposite problem of @aspnet/signalr. While we don't want people to think SignalR can only be used with .NET, we also don't want people to think it can only be used with Azure! It can be used in either environment and works great in each.

4. @microsoft/signalr makes it clear it's the official SignalR client, produced by Microsoft. Other SignalR components can still be named things like @microsoft/signalr-... (like the MessagePack protocol library). It doesn't create brand new NPM orgs (there is already an @microsoft

In the end @microsoft/signalr was the clearest choice. Since it is somewhat disruptive to rename package names, we don't really expect to do it again, getting to something that is truly general (@microsoft) means we'll be happiest to live with it for a long time and avoid disrupting the ecosystem any more.

[analogrelay]

MOVED discussion of the future of @aspnet/signalr to #11688 to avoid adding noise to this thread.

[benaadams]

@anurse need to update the docs https://docs.microsoft.com/en-gb/aspnet/core/tutorials/signalr?view=aspnetcore-3.0&tabs=visual-studio-code

[MarkSFrancis]

The docs also need updating here:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/signalr-typescript-webpack?view=aspnetcore-3.0&tabs=visual-studio#enable-client-and-server-communication

[BrennanConroy]

Tracked at dotnet/AspNetCore.Docs#14794 feel free to fix it if you'd like!

[ghost]

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!