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

@flexshopper/hapi-pres

v3.1.0

Published

Hapi plugin to autoload pres.

Downloads

9

Readme

@flexshopper/hapi-pres

Build Status Dependencies Dev dependencies

Plugin to autoload pres based on patterns.

How to use:

  • Install hapi-pres npm package in your project our plugin. npm i @flexshopper/hapi-pres
  • Register plugin in your hapi server:

Registering

Kraken service style:

const server = new Hapi.Server();

server.connection();

server.register({
    register: require('hapi-routes'),
    options: {
        relativeTo: proccess.cwd() + '/pres',
        includes: ['path/to/**/*pres.js'],
        ignore: ['*.git'],
    }
}, (err) => {
  // continue application
});

Manifest style:

registrations: [
    ...
    {
        plugin: {
            register: 'hapi-pres',
            options: {
                relativeTo: proccess.cwd() + '/pres',
                includes: ['path/to/**/*pres.js'],
                ignore: ['*.git'],
            }
        }
    }
];

Options

includes

Required Type: array

The glob pattern you would like to include

ignore

Type: array

The pattern or an array of patterns to exclude

relativeTo

Type: string

The current working directory in which to search (defaults to process.cwd())

Pre-requirement Signature(Version 2.x.x and before)

const internals = module.exports = {};

internals.assign = 'myAwesomePre';
internals.method = (request, reply) => {
    return reply(request.query);
};

// then in the routes
server.route({
    method: 'GET',
    path: '/ping',
    config: {
        pre: [
             server.pre.myAwesomePre
        ],
        handler: (request, reply) => {
             return reply(request.pre.example);
        }
    }   
});

Pre-requirement Signature(Version 3.x.x and after)

// in you pre-handler file
const internals = module.exports = {};

internals.myAwesomePre = (request, reply) => {

    return reply('myAwesomePre');
}

internals.mySecondAwesomePre = (request, reply) => {
    
    return reply('mySecondAwesomePre');
}

// assume your pre-handler file name is my-Pre.js
// then in the routes
server.route({
    method: 'GET',
    path: '/ping',
    config: {
        pre: [
            server.pre.myPre.myAwesomePre,
            server.pre.myPre.mySecondAwesomePre
        ],
        handler: (request, reply) => {
            return reply('handler');
        }
    }
});

// if you need to get result from pre handler
request.pre.myAwesomePre
request.pre.mySecondAwesomePre

Cautions

  • Please do not name two different pre-handlers with same name, even in different files. Otherwise they won't be accessed correctly.