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

@bodao-corp/hapi-query-qs

v1.0.7

Published

Hapi Plugin to parse query Params in the qs format that acepts [] square brackets

Downloads

15

Readme

Hapi Query String qs

Build Status NPM version Downloads

The purpose of this plugin is to parse the query parameters into a object that is accessible via request.queryqs.

the objetive is to allow 'brackets' '[]' in the querystring and permit hapi too support the kind of query string parsed by the qs package: Examples:

// GET /search?q=tobi+ferret console.dir(req.query.q) // => 'tobi ferret'

// GET /shoes?order=desc&shoe[color]=blue&shoe[type]=converse console.dir(req.query.order) // => 'desc'

console.dir(req.query.shoe.color) // => 'blue'

console.dir(req.query.shoe.type) // => 'converse'

// GET /shoes?color[]=blue&color[]=black&color[]=red console.dir(req.query.color) // => ['blue', 'black', 'red']

HOW TO USE THE PLUGIN?

To use it you just have to register it. After registering it you will have a new object in the request and whenever you need to use the parameters received after the query mark of the url ('?') they will be available getting the query.qs value

Ex: route handler: function (request, reply) { ...

const parsed_parameters = request.query.qs

}

Registering the Plugin

var Hapi = require('@hapi/hapi');
var server = new Hapi.Server();

server.register([
  {
    register: require('hapi-query-qs'),
    options: {
      ignoredKeys: ['count', 'offset'], // Array of query parameters not to convert to filter object
      defaultEnabled: true // if true plugin will be used on all routes
    }
  }
], function (err) {
  // An error will be available here if anything goes wrong
});

Ignoring Keys

You can ignore keys to have them stay at the root level of request.query. A configuration of:

var Hapi = require('@hapi/hapi');
var server = new Hapi.Server();

server.register([
  {
    register: require('hapi-query-qs'),
    options: {
      ignoredKeys: ['count', 'offset'], // Array of query parameters not to convert to filter object
      defaultEnabled: true // if true plugin will be used on all routes
    }
  }
], function (err) {
  // An error will be available here if anything goes wrong
});

Will cause a request like /shoes?order=desc&shoe[color]=blue&shoe[type]=converse to create a request.query.qs that looks like:

{
  order: 'desc',
  
  shoe: {
    color: 'blue',
    type: 'converse'
  }
}

Enabling at the Route Level

If defaultEnabled: false you will need to enable the plugin an a per-route basis by doing the following:

var Hapi = require('@hapi/hapi');
var server = new Hapi.Server();

server.register([
  {
    register: require('hapi-query-qs')
  }
], function (err) {
  // An error will be available here if anything goes wrong
});

server.route({
  method: 'GET',
  path: '/test',
  handler: function (request, reply) { ... },
  options: {
      plugins: {
      hapi-query-qs: {
        enabled: true,
        ignoredKey: ['count', 'offset'], // Array will be concatenated with the ignoredKeys set at register
        params: ['test_param'] // Array of request.params that will be put into filter object
      }
    }
  }
})