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

wurst

v5.0.4

Published

directory based autoloader for hapi.js routes

Downloads

1,136

Readme

wurst logo

Directory based autoloader for hapi.js routes

Travis node npm standard npm

  1. Introduction
  2. Installation
  3. Usage
  4. Example
  5. Testing
  6. Contribution

Introduction

wurst is a directory based autoloader for hapi.js routes. Just set up your desired directory structure, export your route files, register the plugin and get your final prefixed routes based on the provided directory structure. For example it is perfect for manage the various versions of your API. wurst is the German translation for sausage - just throw anything in a pot and in the end you'll be satisfied ;-)

The modules standard and tape are used to grant a high quality implementation.

Compatibility

| Major Release | hapi.js version | node version | | --- | --- | --- | | v5 | >=18.4 @hapi/hapi | >=12 | | v4.1 | >=18.3.1 @hapi/hapi | >=8 | | v4 | >=18 hapi | >=8 | | v3 | >=17 hapi | >=8 | | v2 | >=13 hapi | >=6 |

Installation

For installation use the Node Package Manager:

$ npm install --save wurst

or clone the repository:

$ git clone https://github.com/felixheck/wurst

Usage

Import

First you have to import the module:

const wurst = require('wurst');

Create hapi server

Afterwards create your hapi server and the corresponding connection if not already done:

const hapi = require('@hapi/hapi');
const server = hapi.server({
  port: 8888,
  host: 'localhost',
});

Registration

Finally register the plugin and set the correct options:

(async () => {
  await server.register({
    plugin: wurst,
    options: {
      ignore: 'foo/**/*.js',
      cwd: path.join(__dirname, 'routes'),
      log: true
    },
  })
})();

Options

  • routes: string Optional. Default: **/*.js The glob pattern to select route files.

  • ignore: string | Array.<?string> Optional. The glob pattern or an array of patterns to exclude route files.

  • cwd: string Optional. Default: process.cwd() The absolute path to the current working directory in which to search. Subdirectories will be prefixes.

  • log: boolean Optional. Default: false If true, the plugin logs the prefixed routes into console. For example:

Wurst prefixed the following routes
  [GET]   /foo/bar/foobar
  [POST]  /foo/foo

Example

The following file structure is the base of this example:

src/
..routes/
....routes.js
....bar/
......routes.js
......foo/
........routes.js
..index.js

The route files **/routes.js have to provide a single route object or a list of route objects via module.exports and could look like:

const routes = [
  {
    method: 'GET',
    path: '/',
    handler() {
      return 'foo';
    }
  },
  {
    method: 'GET',
    path: '/42',
    handler() {
      return '42';
    }
  }
];

module.exports = routes;

After starting the server the following routes are available. Trailing slashes - excepted at / - will be removed automatically.

[GET] /
[GET] /42

[GET] /bar
[GET] /bar/42

[GET] /bar/foo
[GET] /bar/foo/42

Testing

First you have to install all dependencies:

$ npm install

To execute all unit tests once, use:

$ npm test

or to run tests based on file watcher, use:

$ npm start

To get information about the test coverage, use:

$ npm run coverage

Contribution

Fork this repository and push in your ideas.

Do not forget to add corresponding tests to keep up 100% test coverage.