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

nn-error-ex

v1.0.0

Published

Functions for creating error messages.

Readme

NN-ERROR-EX

This package includes functions for creating a standardized error message. The messages are in the formatted into a string that looks like: scope-name:message|arguments. The message may also be divided into segments using the ':' character. Using multiple segments will allow error messages to have more context. For example, the message scope:component:message can be divided into 'scope', 'component', 'message'.

Functions

  • createScope( name: string, configuration: ScopeConfiguration ): ErrorScope
    • name: string - The scope name. The name will appear before each message.
    • configuration: ScopeConfiguration - See Scope Configuration

Error Scope

The ErrorScope provides these functions:

  • createErrorMessage( message: string, ...args: unknown[] ): ErrorScope

    • Creates an error message and appends the arguments.
    • Parameters
      • message: string - The message.
      • arg: unknown - A value to include with the message.
  • parseErrorMessage( message: string ): [ string[], string[] | undefined ]

    • Parses an error message.
    • Parameters
      • message: string - The message.
    • The return value is an array with the first value being an array of message segments and the second value being an array of arguments.

Scope Configuration

  • argumentDelimiter: string - The delimiter used to separate the error message arguments. Default is '|'.
  • messageDelimiter: string - The delimiter used to separate the error message segments. Default is ':'.