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

glee

v2.0.4

Published

Specify environment-specific scopes for your routes with ease.

Downloads

24

Readme

Glee for Hapi

Don't want to show certain test routes on production? use Glee! Glee allows you to specify environment-specific scopes for your routes with ease. It utilizes minimatch to compare a route's optional scope to the current node environment, and will filter out any routes from the array that don't match the criteria before registering them.

Install

npm install glee

Example

If a route's scope is set to

!production

The route will be registered when the environment is not "production". Conversely, if the route's scope is set to

development

The route will only be registered if the environment is "development".

Advanced

Given the following scope:

+(development|staging)

The route will be registered if the environment is either "development", or "staging". You can read more about using minimatch here.

Usage

/**
 * Step 1. Define the routes.
 */
var routes = [
  {
    method: 'GET',
    path: '/',
    handler: function (request, reply) {
      return reply('Hello, World.\n');
    }
  }, {
    method: 'GET',
    path: '/ping',
    handler: function (request, reply) {
      return reply('Pong!\n');
    },
    config: {
      plugins: {
        glee: {
          // Register this route only if the environment
          // is not "production".
          scope: '!production'
        }
      }
    }
  }
];

/**
 * Step 2. Register the plugin.
 */
server.register([
  {
    register: require('glee'),
    options: {
      routes: routes,
      environment: 'development'
    }
  }
], function (err) {});
options

|Name|Type|Description|Required| |----|----|:----------|:------:| |routes|array|Our Hapi routes.|Yes| |environment|string|The server environment. This is what we will compare a route's scope to. Defaults to process.env.NODE_ENV|No|

Authors

License

MIT