npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@neistow/ngx-signalr

v1.0.1

Published

Reactive SignalR wrapper for all your needs

Downloads

6

Readme

ngx-signalr

Angular wrapper for @microsoft/signalr.

Installation

npm install @neistow/ngx-signalr
# or
yarn add @neistow/ngx-signalr

Usage

1. Import the NgxSignalrModule

In order to use ngx-signalr in your project you have to import NgxSignalrModule.forRoot() in root NgModule of your application. This method allows you to configure NgxSignalrModule by specifying base url of your application and plenty of other useful configurations.

Configuration interface looks like this:

interface HubConfiguration {
  baseUrl?: string;
  methodNamingPolicy?: MethodNamingPolicy,
  logLevel?: LogLevel;
  retryPolicy?: IRetryPolicy | number[];
  connectionOptions?: IHttpConnectionOptions;
}

2. Create interfaces that describe your hub methods

Create interfaces that mock defined SignalR hub method on your server:

export interface MyHubCommands {
  throw(message: string): Observable<string>;
}

export interface MyHubEvents {
  catch: Observable<[string, number]>;
  ping: Observable<Date>;
}

3. Inject HubFactory and create hub instance

Now you can freely create hub instances via HubFactory and listen to server events and invoke commands. Also don't forget to call connect() and disconnect() methods in appropriate places. Usually you want to do it in OnInit and OnDestroy hooks.

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
})
export class AppComponent implements OnInit, OnDestroy {

  private testHub: Hub<TestHubCommands, TestHubEvents>;

  public serverPing$: Observable<Date>;
  public serverMessage$: Observable<[string, number]>;

  constructor(
    private hubFactory: HubFactory
  ) {
    this.testHub = this.hubFactory.createHub<TestHubCommands, TestHubEvents>('test');
    this.serverPings$ = this.testHub.listen.ping;
    this.serverMessage$ = this.testHub.listen.catch;
  }

  public ngOnInit(): void {
    this.testHub.connect();
  }

  public ngOnDestroy(): void {
    this.testHub.disconnect();
  }
}

4. Alternative usage

If your child components need to use your hub you can use provideHub helper function to leverage angular local providers. provideHub function accepts injection token of your hub and hub name as a parameters and creates a provider under the hood using HubFactory.

The only thing you left to do is inject hub via token in parent and descendants. Hub instance will the same during all injections.


// 0. Describe interfaces
interface MyHubCommands {
  doSomething(): Observable<void>;
}

interface MyHubEvents {
  listenToSomething: Observable<Date>;
}
type MyHub = Hub<MyHubCommands, MyHubEvents>;

// 1. Create hub injection token
const MY_HUB_TOKEN = new InjectionToken<MyHub>('My Hub');

@Component({
  selector: 'app-parent',
  templateUrl: './app-parent.component.html',
  styleUrls: ['./app-parent.component.scss'],
  providers: [
    provideHub(MY_HUB_TOKEN, 'my-hub')
  ]
})
export class AppParentComponent implements OnInit, OnDestroy {
  
  // 2. Inject hub by crearted token
  constructor(
      @Inject(MY_HUB_TOKEN) private myHub: MyHub
  ) {
  }

  // 3. Use it!
  public ngOnInit(): void {
    this.myHub.connect();
  }

  public ngOnDestroy(): void {
    this.myHub.disconnect();
  }
}