c4eb501343
* Emit warnings after off is called If a handler has been registered, and then gets unregistered, the key/methodname still exists in the map and signalr does not warn about a missing handler. Might be by design, but I like it this way. |
||
|---|---|---|
| .. | ||
| build | ||
| spec | ||
| src | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
| rollup.config.js | ||
| tsconfig.json | ||
README.md
JavaScript and TypeScript clients for SignalR for ASP.NET Core
Installation
npm install @aspnet/signalr
Usage
Browser
To use the client in a browser, copy *.js files from the dist/browser folder to your script folder include on your page using the <script> tag.
Node.js
The following polyfills are required to use the client in Node.js applications:
XmlHttpRequest- alwaysWebSockets- to use the WebSockets transportEventSource- to use the ServerSentEvents transportbtoa/atob- to use binary protocols (e.g. MessagePack) over text transports (ServerSentEvents)
Example (Browser)
let connection = new signalR.HubConnection('/chat');
connection.on('send', data => {
console.log(data);
});
connection.start()
.then(() => connection.invoke('send', 'Hello'));
Example (NodeJS)
const signalR = require("@aspnet/signalR");
let connection = new signalR.HubConnection('/chat');
connection.on('send', data => {
console.log(data);
});
connection.start()
.then(() => connection.invoke('send', 'Hello'));