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

message-handler

v0.0.17

Published

Message handler for node

Downloads

5

Readme

Message handler

Setup

To setup messages a json file with the following structure is needed

{
  "1": {
    "1001": {
      code: 1001,
      msg: "example text"
      // can be as many as you need
    },
    "1002": {
      code: 1002,
      msg: "example text"
      // can be as many as you need
    }
  },
  "2": {
    "2001": {
      code: 2001,
      msg: "example text"
      // can be as many as you need
    },
    "2002": {
      code: 2002,
      msg: "example text"
      // can be as many as you need
    }
  }
}

You can structure the json anyway you want within the example above.

And now to initialize the json object you run

const mh = require('message-handler');
mh(__dirname + '/path/to/file');

Variables

In the json you can write variables which will be replaced by a string, number or object. This is achieved with '$!{number}' in the following way (there can be as many as you need)

{
  "1": {
    "1001": {
      code: 1001,
      msg: "$!1", // Var
      type: "$!2" // Var
      // can be as many as you need
    },
    "1002": {
      code: 1002,
      msg: "example text"
      // can be as many as you need
    }
  },
  "2": {
    "2001": {
      code: 2001,
      msg: "example text"
      // can be as many as you need
    },
    "2002": {
      code: 2002,
      msg: "example text"
      // can be as many as you need
    }
  }
}

Then to use the handler run the following function

console.log(
  mh.messageHandler(1001, [
    'Example text', // This will replace $!1 with the text in message 1001
    { // This will replace $!2 with the object in message 1001
      test: example,
      example: test
    };
  ])
);

( you dont need to give an array )

Known issues

If there are 2 instances of setup being ran there will be an overwrite Working on a fix