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

@macalinao/solana-errors

v0.4.0

Published

Solana error message formatting - works in production without __DEV__ flag

Readme

@macalinao/solana-errors

Solana error message formatting that works in production.

Unlike @solana/errors, which strips its message catalog when __DEV__ is false, this package includes the full messages by default — so you can show users a real explanation rather than an error code.

Usage

import {
  getInstructionErrorMessage,
  getTransactionErrorMessage,
} from "@macalinao/solana-errors";

getTransactionErrorMessage("BlockhashNotFound");
// "Blockhash not found in recent blockhashes or in the blockhash queue"

getInstructionErrorMessage({ Custom: 6000 });
// "Custom program error: 0x1770 (6000)"

Stripping messages from your bundle

The message tables cost roughly 6 KB minified. If you would rather ship error codes than prose, define __GRILL_ERROR_MESSAGES__ as false and your bundler will drop them as dead code:

// vite.config.ts
export default defineConfig({
  define: { __GRILL_ERROR_MESSAGES__: "false" },
});
// webpack
new webpack.DefinePlugin({ __GRILL_ERROR_MESSAGES__: false });

The functions then return the variant name instead of its description:

getTransactionErrorMessage("BlockhashNotFound");
// "Transaction error: BlockhashNotFound"

Two caveats:

  • The tables are only dropped if you do not import INSTRUCTION_ERROR_MESSAGES or TRANSACTION_ERROR_MESSAGES directly.
  • Your bundler has to re-run dead-code elimination after constant folding. Rollup, rolldown, and Vite do. Plain esbuild and bun build fold the branch but keep the now-unreferenced tables.

ERROR_MESSAGES_ENABLED exports the resolved value of the flag if you need to branch on it yourself.

License

Apache-2.0