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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@my-oneapp/common

v1.0.14

Published

This package contains shared code and utilities used across the MyMTN-Backend microservices architecture.

Readme

Common Library

This package contains shared code and utilities used across the MyMTN-Backend microservices architecture.

Installation

npm install @my-oneapp/common

Features

Error Handling

Located in /src/errors:

  • BadRequestError - For invalid request handling
  • CustomError - Base error class for consistent error formatting
  • DatabaseConnectionError - Database connectivity issues
  • NotAuthorizedError - Authentication/Authorization failures
  • NotFoundError - Resource not found errors
  • RequestValidationError - Request validation failures

Constants

Located in /src/constants:

  • config.ts - Shared configuration constants
  • roles.ts - User role definitions
  • statuses.ts - Common status codes and messages

Middleware

Located in /src/middlewares:

  • current-user.ts - Extracts and validates current user from JWT
  • error-handler.ts - Global error handling middleware
  • require-auth.ts - Authentication middleware
  • validate-request.ts - Request validation middleware

Events

Located in /src/events:

  • subjects.ts - Event subjects for message broker communication

Utils

Located in /src/utils:

  • jwt.ts - JWT token management (signing, verification)
  • logger.ts - Centralized logging utility
  • response.ts - Standardized API response formatting

Usage Examples

Error Handling

import { NotFoundError } from "@my-oneapp/common";

if (!user) {
  throw new NotFoundError("User not found");
}

Authentication

import { requireAuth } from "@my-oneapp/common";

router.post("/api/resource", requireAuth, (req, res) => {
  // Only authenticated users can access this route
});

JWT Operations

import { JWT } from "@my-oneapp/common";

// Sign a new token
const token = JWT.sign({
  id: user.id,
  email: user.email,
  role: user.role,
});

// Verify a token
const payload = JWT.verify(token);

Response Formatting

import { Response } from "@my-oneapp/common";

res.json(Response.success("Operation successful", data));
res.json(Response.error("Operation failed", error));

Environment Variables

The library requires the following environment variables:

  • JWT_SECRET - Secret key for JWT operations
  • NODE_ENV - Environment name ('development', 'production', 'test')

Contributing

  1. Create a feature branch from main
  2. Make your changes
  3. Update tests if necessary
  4. Submit a pull request

Testing

npm run test

Building

npm run build

The build output will be in the /build directory.

License

Internal use only - MyMTN Backend Services