aspnetcore/client-ts/signalr
Andrew Stanton-Nurse f58ea8133b
fix #1387 by removing our hacky EventSource typings (#1393)
2018-02-01 14:13:08 -08:00
..
build
spec fix #1155 by renaming signalRTokenHeader to access_token (#1343) (#1359) 2018-01-28 14:52:28 -08:00
src fix #1155 by renaming signalRTokenHeader to access_token (#1343) (#1359) 2018-01-28 14:52:28 -08:00
README.md
package-lock.json
package.json
rollup.config.js
tsconfig.json fix #1387 by removing our hacky EventSource typings (#1393) 2018-02-01 14:13:08 -08:00

README.md

JavaScript and TypeScript clients for SignalR for ASP.NET Core

Installation

npm install @aspnet/signalr-client

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 - always
  • WebSockets - to use the WebSockets transport
  • EventSource - to use the ServerSentEvents transport
  • btoa/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'));