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

stubbing

v0.0.7

Published

JSON REST API for NodeJS from file system.

Downloads

15

Readme

stubbing

#JSON REST API from file system.

Inspired by Stubb

command line parameters

-p  server port
-t  response timeout
-d  directory where the api is defined

option object when used as module

{
  baseDir: 'foo',
  timeout: 0
}

javascript over json

If a certain JSON file must be handled, create a JS file with same name in the same directory. The server will load the JS file and the JSON file is ignored.

The JS file should be like this:

var fs = require('fs'),
    path = require('path');

var file = path.resolve(__dirname,'GET.json');

module.exports = function(params, req, ok) {
    fs.readFile(file, function (err, data) {
        if (err) {
            ok('Error: ' + err, null)
        }

        var json = JSON.parse('' + data);

        return ok(null, json);
    });
};

so, a normal NodeJS stuff.

Response Sequences

Yes, are present, like in Stubb link above, needs more work as there are some untreated cases.

Stubb differences

All files must have extensions: JSON and JS.

CORS by default.

Returned headers are not configurable, yet.

Parameters for URL are defined with a _ in front of the name, NO need for another one at the end.

TODO

On error improve the response code. - Today the response is 500, in some cases a 404 is more appropriate.