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

hapi-views

v8.3.2

Published

Hapi view plugin

Downloads

53

Readme

hapi-views

Build Status Coverage Status

hapi-views is a hapi plugin that lets you quickly and easily create your view routes. You use JSON to specify routes that can pull in dynamic data from any source, then use that data to render an HTML page.

Features

  • works with any Hapi view engine
  • define view routes with JSON instead of programming route handlers
  • specify dynamic JSON for your views with varson
  • pull in data with Hapi server methods

Usage

await server.register({
  plugin: require('hapi-views'),
  options: {
    // 'globals' (optional) specifies global data that is common to all views
    // data.serverName and data.db will be available to the view engine:
    globals: {
      serverName: 'Bob the Server',
      db: 'http://55.55.55.5555:2121/bobDb'
    }
    // "routes" can contain as many view routes as you like
    // the key is the URL and the value is an object that specifies how to process the view for that URL
    routes: {
      // the URL for this route will be 'http://yourhost.com/homepage/{userId}'
      '/homepage/{userId}': {
        // 'view' (required) tells the view engine what HTML template to use:
        view: 'homepage',
        // 'data' (required) tells the view engine what context data to use when rendering the HTML
        // this data is itself processed by the template engine in varson:
        data: {
          // an example of a literal string value:
          title: "Your Homepage",
          // varson evaluates string values inside the double-bracket '{{' delimiters as Javascript.
          // So the view engine will see data.amount as 35:
          amount: "{{ 15 + 25 }}",
          // the Hapi request object (https://hapijs.com/api#request) can be referenced directly:
          userId: "{{request.params.userId}}",
          // Hapi server methods (https://hapijs.com/api#server.method()) can be referenced as 'methods'.
          // for example, this expression will set data.userInfo to the value returned by calling server.methods.getUserInfo. Works for methods that return a promise as well:
          userInfo: "{{methods.getUserInfo(request.params.userId)}}"
        },
        // 'preProcess' (optional) will be called before the request is processed:
        preProcess: (request, options, h) => {  }
        // 'preResponse (optional) will be called after the request is processed but before the view is returned:
        preResponse: (request, options, h) => { processRan = true; }
        // 'onError' (optional) will be called if there is an error processing your data or view.
        // The value returned by onError will be the result your route returns to the client:
        onError: (err, h) => { return boom.badImplementation('this was an error') }
      }
    }
  }
});

See test/test.global.js for working examples.