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

node-stubby-server-cli

v1.0.0

Published

Node module which exposes Stubby Server CLI to node

Downloads

64

Readme

node-stubby-server-cli

Module which exposes the Stubby Server API interface from node. The API is clean and simple to use. Note that if you mute() the client, you cannot get any events so it's NOT recommended to do this.

We also use ES6 weakmaps to make certain properties private, however, a polyfill is included in the event your application isn't ES6 ready. Please fork and enhance or file a bug ticket if you notice any issues

ES6

node --harmony <script>.js

< ES6

node <script>.js

Installation

Install this module via npm

npm -i node-stubby-server-cli

Example usage

var cli = new CLI();

cli.admin(8001)
  .stubs(8000)
  .tls(8002)
  .help() // prints the help... note you still chain
  .mute() // supress output
  .data(__dirname + '/data.yml')
  .unmute() // enable output
  .start()
  .on(cli.events.REQUEST, function(data) {
    console.log(data);
  }).on(cli.events.RESPONSE, function(data) {
    console.log(data);
  });

  // server should be running after this...
  cli.once('LISTENING', function() {
     next();
  })
   .on(Events.REQUEST, function(payload) {
    // do something
   })
   .on(Events.DISCONNECTED, function() {
     // do something
   })
   .on(Events.LOADED_ROUTE, function(data) {
    // do something
   })

  // note events won't be dispatch if muted

Example data file (routes)

 [{
   "request": {
     "url": "^/my-api/",
     "method": "GET",
     "body": "Hello World"
   },
   "response": {
     "status": 200,
     "headers": {
       "Content-Type": "application/json"
     },
     "file": "data.json"
   }
 }]

Gulp.js Example

var gulp = require('gulp');
var mocha = require('gulp-mocha');
var StubbyCLI = require('node-stubby-server-cli');
var Events = stubbyCLI.Events;

gulp.task('start:stubby', function(next) {
  var cli = new StubbyCLI.CLI();
  cli.admin(<admin port>)
    .stubs(<stubs port>)
    .tls(<tls port>)
    .data(<path to data file>)
    .unmute()

  cli.once('LISTENING', function() {
    next();
  }).start();
});

gulp.task('test', ['start:stubby'], function() {
  // run your tests after the stub server starts
});

gulp.task('stop:stubby', ['test'], function(next) {
  cli.kill();
  next();
});

// Default tasks to run
gulp.task('default', [
  'start:stubby',
  'test',
  'stop:stubby'
]);

Event.REQUEST Payload

{ 
  "time": "10:27:25",
  "method": "GET",
  "location": "stubs",
  "path": "/hello"
}

Event.RESPONSE Payload

{
  "time": "09:26:47",
  "statusCode": "404",
  "location": "stubs",
  "path": "/your/awesome/endpoint",
  "message": "is not a registered endpoint"
}

Test

npm test