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 🙏

© 2026 – Pkg Stats / Ryan Hefner

va-mellower

v1.5.7

Published

logistics for va

Downloads

2

Readme

mellower

logistics is boring

Mock

mock config in your package.json

{
    va-mock: {
        routes: './mock/routes.js',
        config: {
            mergeResponse: false
        }
    }
}

routes example, refer to lib/example/xxx.routes.js

[
    {
        url: 'rest/:tenantid/virtual-agent/intent',
        method: 'get',
        response: intents,
        handler: (ctx, resp) => {
            const { query } = ctx;
            ctx.body = resp;
            if (query.recommended || query.recommended === 'true') {
                ctx.body = resp.filter(intent => intent.recommended === true);
            }
            if (query.name) {
                ctx.body = resp.find(item => item.name === query.name);
            }
        }
    }
]

handler function arguments:

  • ctx is context of your request
  • resp is the response property above.

How to use mock in my project

  1. npm install xxxxx
  2. update your package.json, add below field:
"va-mock": {
    "port": 5000,
    "config": {
      "mergeResponse": true // tell mocker what to do with your route response and sample route response, if there is existing route in sample.
    },
    "routeFile": "" // your route definition, json with array of object.
  }
  1. run command va-mock

Validator

currently the validation works for va only.

// you want to validate intent definition
// node.js
const { asyncValidate } = require('@micro-focus/va-mellower');
const intent = {/*some properties*/};
await asyncValidate('Intent', intent, ctx);
// ctx is current request context, such as ctx of KOA or Eggjs
// if you use it in frontend, no need to pass ctx.

where to put this mellower package in your package.json

if you just use the mock service, put it in devDependencies
if you use validation, put it in dependencies
release build will only check dependencies

build

  • build will happen when commit
  • only validation will be built
  • mocker is for backend(cjs only) , so no need to build