updating signalr js package readme

[bradygaster]

per the doc issue reported here, this update makes it more up-front which client customers should use, when their only knowledge of SignalR Is from perusing NPM packages, or who find their way here via OG SignalR docs.

wasn't sure which branch to suggest as upstream - goal here is simply to update the npm readme for the pre-@microsoft/signalr era.

[ghost]

Hello human! Please make sure you've included the Shiproom Template in a comment or (preferably) the PR description. Also, make sure this PR is not marked as a draft and is ready-to-merge.

[BrennanConroy]

We need to update the patch config

aspnetcore/eng/PatchConfig.props

Line 65 in d4f43e7

<PackagesInPatch>

Add @aspnet/signalr

[wtgodbe]

@BrennanConroy we need to re-ship this package with the updated readme?

[BrennanConroy]

Yes, we're trying to update the README on npm which needs a published package with the update.

[BrennanConroy]

???

[dougbu]

Well, that's not good. 21 commits is much more than I expected. Did you perhaps rebase on release/3.1❔ Or is this just another GitHub UI oddity❔

[BrennanConroy]

Well, that's not good. 21 commits is much more than I expected. Did you perhaps rebase on release/3.1❔ Or is this just another GitHub UI oddity❔

Neither which is why this is super annoying.

[dougbu]

this is super annoying.

Yes

[BrennanConroy]

Fixed

[dougbu]

Was the issue an incomplete rebase i.e. having conflicts when pushing❔

[BrennanConroy]

Having a different remote that was ~21 commits behind :/

[dougbu]

Please ping when checks complete and you've confirmed the npm package is created correctly. @wtgodbe or I will get it in.

[BrennanConroy]

Npm package created and build passed 👍