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

prisma-error-formatter

v1.0.1

Published

A flexible and customizable Prisma error formatter for better error handling and user-friendly error messages in Prisma Client applications.

Readme

prisma-error-formatter

npm version
License: MIT

A flexible and customizable Prisma error formatter to simplify and unify error handling in Prisma Client applications. Easily transform Prisma errors into user-friendly, consistent error messages for your APIs or UI.


Features

  • Formats common Prisma Client errors like unique constraint violations, foreign key errors, validation errors, and initialization errors.
  • Supports custom error formatting via a callback function.
  • Works with Prisma Client’s error classes:
    • PrismaClientKnownRequestError
    • PrismaClientValidationError
    • PrismaClientInitializationError
    • PrismaClientRustPanicError
  • Returns structured error messages with clear path and message fields.
  • Written in TypeScript with full typings.

Installation

npm install prisma-error-formatter @prisma/client

Basic Usage

import { PrismaClient } from "@prisma/client";
import { PrismaExceptionFormatter } from "prisma-error-formatter";

const prisma = new PrismaClient();
const formatter = new PrismaExceptionFormatter();

async function createUser(email: string) {
  try {
    await prisma.user.create({ data: { email } });
  } catch (error) {
    const formattedErrors = formatter.formatError(error);
    console.error(formattedErrors);
    /*
      Example output:
      [
        {
          path: "email",
          message: "A record with this email already exists."
        }
      ]
    */
  }
}

Using a Custom Formatter

You can provide your own formatting logic by passing a format function when creating the formatter instance:

import { PrismaExceptionFormatter, ErrorMessage } from "prisma-error-formatter";

const formatter = new PrismaExceptionFormatter({
  format: ({ type, error, defaults }) => {
    // Add extra info or change messages based on error type
    if (type === "known" && error.code === "P2002") {
      return [
        {
          path: defaults[0].path,
          message: `Custom: Duplicate value found for ${defaults[0].path}`,
        },
      ];
    }
    // Fallback to default formatting
    return defaults;
  },
});

API

new PrismaExceptionFormatter(options?: { format?: FormatFunction })

Creates a new formatter instance.

  • options.format - Optional custom format function. Receives an object with:
    • type: The error type (known, validation, initialization, panic, unknown)
    • error: The original error object
    • defaults: The default formatted error messages (array of { path, message })

Returns formatted errors as an array.

Methods

  • formatError(exception: any): ErrorMessage[]
    Automatically detects the Prisma error type and returns formatted messages.

  • formatPrismaError(exception: PrismaClientKnownRequestError): ErrorMessage[]
    Formats known Prisma client errors.

  • formatQueryError(exception: PrismaClientValidationError | PrismaClientRustPanicError): ErrorMessage[]
    Formats validation or panic errors.

  • formatInitializationError(exception: PrismaClientInitializationError): ErrorMessage[]
    Formats database initialization errors.

  • formatUnknownError(exception: any): ErrorMessage[]
    Formats unknown errors.


Supported Prisma Error Codes (Known Errors)

  • P2002 - Unique constraint violation
  • P2003 - Foreign key constraint failure
  • P2005, P2006 - Invalid value errors
  • P2025 - Record not found

License

MIT © Nurul Islam Rimon


Contribution

Contributions, issues, and feature requests are welcome! Feel free to check

project page

issues page


Related


Built with ❤️ by Nurul Islam Rimon


🛠️ Open Source Contribution

This project is open to all contributors! Whether you're fixing bugs, improving documentation, adding new formatters, or suggesting ideas — your contribution is highly appreciated.

How to Contribute

  1. Fork this repository
  2. Create your feature branch:
    git checkout -b feat/my-awesome-feature
  3. Commit your changes:
    git commit -m "feat: add my awesome feature"
  4. Push to the branch:
    git push origin feat/my-awesome-feature
  5. Open a pull request

🙌 Contributions Welcome!

  • 📖 Improve the documentation
  • 🧪 Add unit tests
  • 🔍 Add support for more Prisma error codes
  • 💡 Propose new formatting strategies or ideas