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

bimedia-front-server

v1.0.0

Published

bimedia front-end test server

Downloads

4

Readme

bimedia-front-server

Bimedia Front-end test server.

features :

  • serve static assets
  • static data fixtures
  • http method to resource mapping
  • proxied data
  • custom test routes

Example :

var server = require('./test-server');
var path = require('path');

var PORT = 9090;

server({
    fixtures : {
        path : path.join(__dirname, './fixtures'),
        prefix : 'api'
    },
    'static' : {
        path : path.join(__dirname, './src')
    }
}).listen(PORT, function () {
    console.log('test server listening on port %d', PORT);
});

This example create a server listening on port 9090 that will serve any static resource availiable in src subfolder. It will also serve JSON data availiable in fixtures folder for every request with the path starting with api.

static assets

Serve files in static.path like any http server.

fixtures

The server tries to find a matching ressource in the filesystem in path denoted by config fixtures.path.

Example:

GET /api/auth/token

will serve file :

$cwd/auth/token.json

method mapping

For any http method other than GET, it will append method name in lowercase at the end of requested uri.

Example:

POST /api/auth/token

will serve file :

$cwd/auth/token-post.json

proxied data

Fixtures can be retrieved from an url. The test server serves proxy data.

Example :

var server = require('./test-server');
var path = require('path');

var PORT = 9090;

server({
    fixtures : {
        url : 'http://my.remotehost.com/fixtures',
        prefix : 'api'
    },
    'static' : {
        path : path.join(__dirname, './src')
    }
}).listen(PORT, function () {
    console.log('test server listening on port %d', PORT);
});

multiple fixtures sources

Fixtures can be retrieved from more than one location, both locally or remotely.

Example :

var server = require('./test-server');
var path = require('path');

var PORT = 9090;

server({
    fixtures : [{
        url : 'http://my.remotehost.com/fixtures',
        prefix : 'api/params'
    },
    {
        path : path.join(__dirname, './fixtures'),
        prefix : 'api'
    }
    ],
    'static' : {
        path : path.join(__dirname, './src')
    }
}).listen(PORT, function () {
    console.log('test server listening on port %d', PORT);
});

custom test routes

Add custom route and logic with routes method.

server({
    fixtures : {
        path : path.join(__dirname, './fixtures'),
        prefix : 'api'
    },
    'static' : {
        path : path.join(__dirname, './src')
    }
}).routes(function (router) {
    router.get(/api\/([0-9]{4}-[0-9]{2}-[0-9]{2})/, function (str) {
        this.res.writeHead(200, {
            'Content-Type': 'text/plain'
        });
        this.res.end(str);
    });
}).listen(PORT, function () {
    console.log('test server listening on port %d', PORT);
});

based on :