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

tiny-jsonrpc-client

v1.1.0

Published

A lightweight JSON-RPC 2.0 client

Downloads

5

Readme

jsonrpc-client

A really, really simple JSON-RPC 2.0 client.

Installation

npm install --save jsonrpc-client

Usage

Simple usage

var jsonRpc = require('jsonrpc-client')

// Our API server is at http://example.org/api
jsonRpc.setUrl('http://example.org/api')
// Let's call the 'saySomething' method that takes two parameters, 'to' and 'message'
jsonRpc.call('saySomething', {to: 'Alice', message: 'Hi, Bob!'})
.then(function success(result) {
  // The 'saySomething' method has a field 'output'
  console.log('output', result.output)
}, function failure(err) {
  // oops, something went wrong!
  console.error('Oops! Error code ' + err.code + ': ' + err.message)
  // additional data might be in 'err.data'
})

Using cookies

If the API is using a cookie to keep track of the session, you can use setUseCookies(true):

var jsonRpc = require('jsonrpc-client')

var SessionCookie = null // store session cookie for later

// Our API server is at http://example.org/api
jsonRpc.setUrl('http://example.org/api')
// Let's call the 'saySomething' method that takes two parameters, 'to' and 'message'
jsonRpc.call('login', {username: 'alice', password: 'monkey'})
.then(function success(loginResult) {
  // The 'getMessages' method has a field 'messages' and requires the cookie from login
  jsonRpc.call('getMessages', {}).then(function(msgResult) {
    console.log('Messages: ', result.messages)    
  })
  SessionCookie = jsonRpc.getCookie() // gets our session cookie for later use (see below)
}, function failure(err) {
  // oops, something went wrong!
  console.error('Oops! Error code ' + err.code + ': ' + err.message)
  // additional data might be in 'err.data'
})

You can also get hold of the cookie using getCookie and setCookie to set a cookie

var jsonRpc = require('jsonrpc-client')

// Our API server is at http://example.org/api
jsonRpc.setUrl('http://example.org/api')

jsonRpc.setCookie(SessionCookie) // the cookie from the example above, holding our session information

// Let's call the 'getMessages' method again without a login but using the cookie
jsonRpc.call('getMessages', {})
.then(function success(result) {
  // The 'getMessages' method has a field 'messages' and requires the cookie from login
  console.log('Messages: ', result.messages)
}, function failure(err) {
  // oops, something went wrong!
  console.error('Oops! Error code ' + err.code + ': ' + err.message)
  // additional data might be in 'err.data'
})