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

bridle

v1.0.2

Published

Javscript black magic RPC over websockets.

Downloads

6

Readme

Bridle: Black magic Javascript RPC

Version npm Linux Build Coverage Status Known Vulnerabilities License

Installation

npm install --save bridle

Bridle allows exporting functions from a Node.js server and then calling them natively from a client (both Node and browsers are supported).

Remote functions will be ran on the server, with communication occurring using WebSocket transport. Local functions will be ran natively on the client as is.

Note: This project exists because it can, not because it should. The author takes no responsibility for any [mis]use.

Usage

Server:

const Bridle = require('bridle');

new Bridle.Server({
    port: 7777,
    localFunctions: {
        foo: () => {
            console.log('bar');
        }
    },
    remoteFunctions: {
        hello: (name) => 'Hello ' + name
    }
});

Client:

import {Client} from 'bridle';

const rpc = new Client();

rpc.connect('ws://localhost:7777')

    .then(functions => {

        functions.foo();

        functions.hello('world!').then(result => {
            console.log(result);
        }).catch(error => {
            console.log(error);
        });
    });

Output:

$ bar
$ Hello world!

Support

Tested in Node.js v6.10.0, Chrome 63

License

ISC