Fix MessagePack JS package peer dependency

[analogrelay]

The @aspnet/signalr-protocol-msgpack package has a peer dependency on @aspnet/signalr. This is good, but the value is static and hasn't been updated since 1.0.0-preview3. We should either add automation to update the peer dependency on every build, or just remove it, or maybe make it a real dependency.

[analogrelay]

It should almost definitely just be a real dependency, in which case we can use a path link and I think the build output will be correct.

[OzBob]

Confirmed.
It also, stops MessagePack messages between JavaScript client and server.

npm i @aspnet/signalr@next
//which installs v "^3.0.0-preview5-19227-01"
npm i @aspnet/signalr-protocol-msgpack@next
//which installs v "^3.0.0-preview5-19227-01"
BUT WARNS:

"npm i @aspnet/signalr-protocol-msgpack@3.0.0-preview5-19227-01 requires a peer of @aspnet/signalr@^1.0.0-preview3 but none is installed. You must install peer dependencies yourself."

that version is NOT available on https://www.npmjs.com/package/@aspnet/signalr

[BrennanConroy]

The warning can be ignored for now, we'll be fixing it up soon.

Those 2 packages should be compatible. Could you share a repro app that shows the issue?

[analogrelay]

This is more complicated than I hoped. If you set it to link:../signalr or file:../signalr, that's exactly what goes in to the package.json, which isn't what we want.

To do this right I think we need to rewrite the package.json during build... I'll tinker with that.

[analogrelay]

@pranavkm is looking at fixing this as part of his send queue change.