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

germaine

v1.0.5

Published

Germaine is an ExpressJs middleware that allows you to quickly deploy an API that listens on a given endpoint and serves content from a JSON file.

Downloads

27

Readme

Germaine is an ExpressJs middleware that allows you to quickly deploy an API that listens on a given endpoint and serves content from a JSON file.

Features

  • dependency free
  • lightweight (3Ko)
  • super-fast
  • delay simulator (for lazy loading tests)
  • dynamic reading
  • Define your endpoints in a funny way :)

Installing

Using npm:

$ npm install germaine

Using bower:

$ bower install germaine

API

germaine(path[, config])

path

The path to the file used as database. It can be JSON or JavaScript.

config

| NAME | TYPE | DESCRIPTION | | :------- | :-----------------------------------------------------------------------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | isStatic | boolean Default: false | By default, the file will be read each time the url is called. This allows you to update the content at any time without having to restart the whole server. You can disable this feature by setting isStatic to true. | | delay | int,object Default: 0 | You can add a custom delay (ms) to the requests. This is useful to simulate lazy loading for example. You can also provide an object with the min and max properties to randomise the delay. |

Example

const express  = require('express');

const germaine = require('../index');

const path     = require('path');

const app = express();

app.get(

  '/germaine/*', 

  germaine(path.resolve(__dirname, './example-database.json'))

);

app.listen(3030, function () {

  console.log('germaine listening on localhost:3030/germaine!');

});

How it works

Let's assume that this JSON represents your database:

{

  "pages": {

    "home": {

      "title": "Home page",

      "content": {

        "intro": "..."

      }

    },

    "bio": {

      "title": "About myself"

    },

    "content": {

      "lastProject": "Germaine"

    }

  }

}

With germaine, you can get access at any depth segment of the file from the url.

For example, you can get the content of the homepage this way :

GET /germaine/pages/home

But you can also only ask for the page title!

GET /germaine/pages/home/title

This let you define more or less complexes structures and sort your content very easily!

When should I use this?

  • When you only need to get static content from a server
  • For building tests
  • When you have to build something that needs to make simple API calls, but the API has not been developed

Can I use it on production?

Yes of course! Germaine is a simple middleware for express, so it's up to you to add any restrictions and controls you which.

What about multi-language?

Germaine would like not to overweight. She therefore does not prefer to transform herself into a multi-function toolbox but remain herself, simple. However, it is always possible for you to cheat a little :

const express  = require('express');

const germaine = require('../index');

const path     = require('path');

const app = express();

app.get('/germaine/*', (req, res) => {

  if (headers['content-language']) {

    const path = `database-${headers['content-language']}.json`;

    return germaine(path.resolve(__dirname, path)(req, res);

  }

}));

app.listen(3030, function () {

 console.log('germaine listening on localhost:3030/germaine!');

});

And if I want to use several JSON files?

Germaine would like not to overweight. She therefore does not prefer to transform herself into a multi-function toolbox but remain herself, simple. However, it is always possible for you to cheat a little :

const express  = require('express');

const germaine = require('../index');

const path     = require('path');

const app = express();

app.get(

  '/germaine/pages*', 

  germaine(path.resolve(__dirname, './pages-database.json'))

);

app.get(

  '/germaine/articles*', 

  germaine(path.resolve(__dirname, './articles-database.json'))

);

app.listen(3030, function () {

console.log('germaine listening on localhost:3030/germaine!');

});

License

MIT