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

mymundo-error-codes

v1.0.4

Published

Centralized error code definitions for MyMundo admin and storefront

Readme

mymundo-error-codes

Centralized error code definitions for MyMundo admin and storefront.

Installation

npm install mymundo-error-codes

Usage

import { ValidationErrorCode } from 'mymundo-error-codes';

// Use validation error codes
const errorCode = ValidationErrorCode.REGISTRY_EMAIL_INVALID_FORMAT;

Development

To build the package:

npm run build

Publishing

Automatic Publishing via CI/CD

This package is automatically published when changes are detected in the packages/be-error-codes directory:

  • When: Changes are detected in src/, package.json, or tsconfig.json
  • Version: Automatically bumps patch version (e.g., 1.0.0 → 1.0.1)
  • Trigger: Runs automatically on commits to main branch
  • Process:
    1. Detects changes in the package
    2. Bumps patch version
    3. Builds the package
    4. Publishes to npm registry
    5. Commits version bump back to repository

Manual Publishing

To publish manually:

npm publish

To use locally in this repo (before publishing), you can:

  • Use yalc (already in your devDependencies)
  • Or add it as a local dependency using npm link or file path

CI/CD Requirements

For automatic publishing to work, ensure the following CI/CD variables are set in GitLab:

  • NPM_TOKEN: npm authentication token with publish permissions

The CI job will:

  • Check for changes in packages/be-error-codes/src/, package.json, and tsconfig.json
  • Only run on the main branch (or manually on other branches)
  • Automatically bump patch version and publish
  • Commit the version bump back to the repository

Exports

ValidationErrorCode (enum)

Validation error codes:

  • REGISTRY_EMAIL_INVALID_FORMAT
  • REGISTRY_EMAIL_TAKEN
  • REGISTRY_VAT_INVALID_FORMAT
  • REGISTRY_PINCODE_INVALID_FORMAT