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

aspnetcore.websocket-provider

v1.0.6

Published

Intended usage with [AspNetCore.WebSockets](https://gitlab.com/ifinnscott/net-core-websockets)

Downloads

3

Readme

net-core-react-websockets

Intended usage with AspNetCore.WebSockets

Register SocketProvider

import React from 'react';
import { render } from 'react-dom';
import { SocketProvider } from '../src/socketProvider';

[...]

const target = document.getElementById('app');
const socketOptions = {
  port: 5001, // If undefined defaults to location.port
  host: 'localhost', // If undefined defaults to location.hostname
  path: 'ws'
};

[...]

const node = (
  <Provider store={store}>
    <SocketProvider options={socketOptions}>
      <Router history={history} onUpdate={onUpdate}>
        {appRoutes}
      </Router>
    </SocketProvider>
  </Provider>
);

render(node, target);

Usage with socketConnect

import React, { Component } from 'react';
import { socketConnect } from '../src/socketProvider';

class App extends Component {
  constructor(props) {
    super(props);

    props.addSocketEvent('debug', this.onSocketDebug);
  }

  onSocketDebug(msg) {
    console.log(msg)
  }

  sendSocketMessage() {
    const { emitSocketEvent } = this.props;

    emitSocketEvent('debug', 'Data Incoming');
    emitSocketEvent('debug', {
      key: 'Value'
    });
  }

  render() { 
    return (
      <div>        
        [...]
      <div>
    );
  }
}

const onConnect = props => {
  console.log(props);
}

const onClose = props => {
  console.log(props);  
}

const onMessage = (data, props) => {
  console.log(data, props);
}

const onError = props => {
  console.log(props);
}

export default socketConnect(App, {
  onConnect: onConnect, 
  onClose: onClose, 
  onMessage: onMessage, 
  onError: onError
});

Access to socket object

import React, { Component } from 'react';
import { socketConnect } from '../src/socketProvider';

class App extends Component {
  constructor(props) {
    super(props);

    const socket = props.socket;
  }  

  render() { 
    return (
      <div>        
        [...]
      <div>
    );
  }
}

export default socketConnect(App, {});

Server side rendering

If you need to server side render the SocketProvider, use it without passing any options

[...]

const createApp = (store, props) => renderToString(
  <Provider store={store}>
    <SocketProvider>
      <RouterContext {...props} />
    </SocketProvider>
  </Provider>
);

[...]