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

librarify

v1.5.0

Published

Create a Node.js library instantly from a REST API

Downloads

26

Readme

Librarify

Create a Node.js library for your REST API with just a settings JSON object

Librarify is a library for creating libraries for REST APIs as easily as possible. When you create a library with Librarify, your library has functions to configure parameter requirements and defaults at a per-function and global basis.

Getting started

$ npm install --save librarify

Usage

Node.js

var Library = require('librarify');

var myLibrary = new Library(settings);

Settings

For each function name in settings.fns, a function with that name will be created. RFC-style names separated by dots are also supported. Examples:

  • setting.fns['foo'] will create myLibrary.foo(params[, callback])
  • settings.fns['foo.bar'] will create myLibrary.foo.bar(params[, callback])

For each of these functions, the callback is not required. If specified, the callback will be executed, otherwise a Promise is returned.

var settings = {
  url : 'https://your.baseurl.com/v1',
  config : {
    key : { // parameter that is required for all function calls
      required : true
    },
    globalFormat : 'pretty' // default value of 'globalFormat' is 'pretty'
  },
  fns : { // list of functions your library will include
    'function_name' : {  
      route : '/routeForFn1', // hits https://your.baseurl.com/v1/routeForFn1.
      type : 'POST' // HTTP request type
      requiredParam : ['you', 'need', 'these'],
      optionalConfig : ['globalFormat'],
      optionalParam : ['nice', 'to', 'haves']
    }
  }
}

var myLibrary = new Library(settings);
options
  • url (required) - you API's root URL.
  • config (optional) - specify default parameter values and requirements. Example:
  config : {
    param1 : true, // required by all calls
    param2 : 'foo', // parameter defaults to 'foo'
    param3 : {
      defaultVal : 'bar',
      required : false
    }
  }
  • fns (optional) - supported functions for your Library
    • name (required) - name of your library function (must be a valid Javascript function name)
      • route (optional) - URL path. Defaults to /function_name
      • type (optional) - HTTP request type. GET, POST, PUT currently supported. Defaults to GET. Parameters are sent as query params for GET requests and as body params elsewise.
      • requiredParam (optional) - array of names of required parameters for this function.
      • optionalConfig (optional) - array of names of optional parameters specified in config for this function, or true to include all config options.
      • optionalParam (optional) - array of names of optional parameters for this function.
Config

All config options can be overidden in function calls. Each config option will be included in every call that is not overidden by the specific function call. Config() is used to set parameters that are needed for all/most of your function calls (think API tokens, keys, or global formatting).

var myLibrary = new Library(settings);

myLibrary.config({
  key : process.env.HIDDEN_KEY,
  global_format : 'pretty'
});

Examples

Also see /examples

This example is for the what3words API

var settings = {
  'url' : 'https://api.what3words.com/v2',
  'config' : {
    key : {
      required : true
    },
    lang : 'en',
  },
  'fns' : {
    'forward' : {
      requiredParam : ['addr'],
      optionalConfig : ['lang', 'format', 'display'],
    }
  }
}

var w3w = new Library(settings);
w3w.config({
  key : process.env.W3W_KEY,
});

w3w.forward({
  addr : 'steep.sober.potato',
  display : 'terse'
}, function (err, res){
  if (err) console.log(JSON.stringify(err, null, 4));
  else {
    console.log(JSON.stringify(res, null, 4));
  }
});

Auto-Generating a README for your library

Requires a JSON settings file that is identical to the one passed into Librarify constructor.

$ npm run readme path_to_settings.json [path_to_output_file]

Coming Soon

  • [x] ~~Support RFC dotted method calleds~~
  • [x] ~~Automatic README generating script~~
  • [x] ~~Multiple HTTP request options (POST, PUT, DELETE)~~
  • [ ] Support specifying individual parameter type: query, body, or header as well as pluggable inline URL params.