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

reflector

v0.0.4

Published

Simple http server used as a stub for testing, will return any parameters sent (with errors if needed).

Downloads

13

Readme

Reflector

Build Status

Simple http server used as a stub for testing, will return any (GET/POST) parameters sent with some meta data as JSON. This allows you to define API calls on the fly, running requests through http, while controlling the expected output.

The server may optionally be configured to send some http errors at times replacing the expected response.

Configuration

  • errors If the server should return errors randomly (~5% of the time), defaults to false.
  • port Port server should use for listening, defaults to 80.

Meta Data

Meta data is helpful for informing tests and debugging. The returned JSON object will also have a property '_meta'. This property contains three values:

  • date When this response was generated.
  • path The request path for this response.
  • count Number of times this path has been requested during the lifetime of the server.

Example

Here is reflector being used in a mocha/should/request test (see a more in-depth example at retainer):


describe('example test', function(){
  var reflector = require('reflector'),
  request = require('request');
  
  var server = reflector({port : 8001});
  before(server.start);
 
  it('should return name-value pairs', function(done){
    request({
      url : 'http://localhost:8001/some/path?someproperty=somevalue&anotherproperty=anothervalue',
      json : true}, function(err, response, json){
	  if(err) return done(err);
	  json._meta.should.be.an.Object.and.have.properties('count', 'date', 'path');
//
// Returned object is:
// { _meta: 
//  { date: '2014-02-16T17:53:27.624Z', // whatever the request time is
//    path: '/some/path', // arbritary path used
//    count: 1 }, // first time this path was used
//  someproperty: 'somevalue',
//  anotherproperty: 'anothervalue' }

	  return done();
    });
  });
  
  after(server.stop);
});