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

@microservice-framework/microservice-websocket

v1.2.4

Published

Websocket based API router. Allow to listen to new messages across API

Downloads

14

Readme

microservice-websocket

Gitter npm microservice-frame.work

Websocket service to provide API access and receive information about new data.

Configure NGINX to proxy WebSocket requests

upstream apiv1ws {
    server api1.server.com:6001;
    server api2.server.com:6001;
}

server {
    listen       443 ssl;
    server_name  my-server.com www.my-server.com;
    underscores_in_headers on;
    large_client_header_buffers 4 64k;
    ssl_certificate ssl/my-server.com.crt;
    ssl_certificate_key ssl/my-server.com.key;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers         HIGH:!aNULL:!MD5;

    location /ws_endpoint/ {
      limit_conn                 conn_from_one_ip 20;
      proxy_pass                 http://apiv1ws/;
      proxy_http_version         1.1;
      proxy_send_timeout         15m;
      proxy_read_timeout         15m;
      proxy_set_header           Upgrade $http_upgrade;
      proxy_set_header           Connection "upgrade";
      proxy_set_header           Host       $host;
      proxy_set_header           X-Real-IP  $remote_addr;
      proxy_set_header           HTTP_X_FORWARDED_FOR  $remote_addr;
      proxy_set_header           X-Forwarded-For $proxy_add_x_forwarded_for;
    }

}
    

WebBrowser Javascript example:

    <script src="http://microservice-frame.work/js/microservice-client.min.js"></script>
    <script>
$(function() {    
    var clientSettings = {
      URL: "wss://my-server.com/ws_endpoint/",
      token: 'secureKey or AccessToken'
    }
    ws = new MicroserviceWebSocket(clientSettings);
    ws.on('message', function(object){
      console.log(object);
    });
});
    </script>