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

jsonrpc2-express

v0.4.4

Published

jsonrpc 2.0 end point for Express.js

Downloads

3

Readme

jsonrpc2-express: JSON-RPC end-point for express

build status

Module to configure an express router in order to expose a JSON-RPC end-point.

Installation

npm install jsonrpc2-express

Usage

const express = require('express');
const jsonrpc = require('jsonrpc2-express')

const app = express();

let routerRpc = express.Router();

jsonrpc('/rpc/module1', routerRpc, {
    methods: require('./module1.js'),
    bodyParser: {
        limit: '50mb'
    }
});

app.use('/api', routerRpc);

app.listen(3000, function() {
    console.log('Server listening on port 3000');
});

The file module1.js with the implementation of the different methods is:

exports.f1 = function(req) {
	console.log(req.body.params)
    return {
	field1: 'answer from f1',
	user: req.user
    };
};

exports.f2 = function(req) {
	console.log(req.body.params)
    return {
	field1: 'answer from f2',
	user: req.user
    };
};

exports.ferror = function(req) {
    throw new Error("sorry");
};

The parameters for each method can be read from req.body.params

Tests

npm test

Contributing

In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.