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

@azhder/explano

v0.0.2

Published

generate short error messages to explain some problem

Downloads

3

Readme

Explano

Use to generate short error messages to explain some problem, like

E123: The problem 123 occured

Install

$ npm install --save @azhder/explano

Include

  • In CommonJS environment
const E = require('@azhder/explano');
  • Using ES modules
import E from '@azhder/explano';

Use

  • On first access, it uses the property name as the returned message
console.log(E['E123: The problem 123 occured']); // E123: The problem 123 occured
console.log(E.AS3113); // AS3113
console.log(typeof E.AS3113); // string
  • Plays nice with JSON.stringify
console.log(JSON.stringify(E.STR1N6)); // "STR1N6"
  • Invoked as a function, it sets property to a new namespace function
console.log(E('FUNCT10N')); // [Function: FUNCT10N]
  • Must set-up sub-namespace functions before their first access (otherwise they will be set as strings)
E('INV0');
E('INV0')('K3D');
  • Sub-namespaces are used as prefixes when accessing the property at the end
console.log(E.INV0.K3D['with some explanation']); // INV0: K3D: with some explanation
  • Sub-namespaces don't work on strings
console.log(E.UND3F1N3D); // UND3F1N3D
console.log(E.UND3F1N3D.T35T); // undefined
  • Memoizes calls for future access. The previous examples will produce an object like the following
console.log(E);


// [Function (anonymous)] {
//     'E123: The problem 123 occured': 'E123: The problem 123 occured',
//     AS3113: 'AS3113',
//     STR1N6: 'STR1N6',
//     FUNCT10N: [Function: FUNCT10N],
//     INV0: [Function: INV0] {
//         K3D: [Function: INV0: K3D] {
//             'INV0: K3D: with some explanation': 'INV0: K3D: with some explanation'
//         }
//     },
//     UND3F1N3D: 'UND3F1N3D'
// }