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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mock-signalr

v0.1.1

Published

A simple signalR server that can be used for mocking and development.

Readme

mock-signalr

A simple implementation of a SignalR server for testing and development purposes.

Currently only supports a single hub and stimulating server push.

Not tested in Linux or Mac yet!

Prerequisites

The SignalR server requires .NET core to be installed. https://dotnet.microsoft.com/download

Getting started

Run the command:

mock-signalR -origins "http://127.0.0.1:8080, http://127.0.0.1:8000" -hub "chatHub" -port 5005

The server can be started uisng the mock-signar command.

  1. You must specify a CORS origin with -origins, for example -origins http://127.0.0.1:8080. Multiple origins can be specified by separating them with a comma, but the origins argument must be contained in quotes, for example: -origins "http://127.0.0.1:80, http://127.0.0.1:8080".

  2. You must specify the hub to mock with the -hub command. For example: -hub chatHub.

  3. A port can be specified with the -port command, for example -port 4000. If not specified it will default to 5000.

  4. You can stimulate the server to send a response by sending a POST command to http://localhost:5000/api/send/{myMethod} (note: use the sepcified port if configured). The body must be a JSON payload.

Development

You can start the sample/testing site by running npm run build-site and npm run start-site.

License

Licensed under MIT.