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

@forst/errors

v0.3.0

Published

Shared tagged error classes for Forst generated clients (invoke transport, harness, unknown failure).

Readme

@forst/errors

Shared tagged error classes for Forst generated TypeScript clients.

Exports

  • @forst/errors Promise mode. Uses a small tagged() helper. No runtime dependencies.
  • @forst/errors/effect Effect mode. Uses Data.TaggedError. Requires the effect peer.

What's included

Invoke transport failures (InvokeRejected, InvokeHttpFailure, …), test harness failures (ForstTestServerFailed), and the domain catch-all (ForstUnknownFailure).

Built-in _tag values are namespaced under @forst/errors/ (for example @forst/errors/InvokeRejected).

Shared invoke, harness, and unknown-failure classes live in this package. Import them directly (@forst/errors in Promise mode, @forst/errors/effect in Effect mode). Generated clients expose optional domain error namespaces from @forst/gen/$errors.

Usage

Prefer matching on _tag in Effect code (Effect.catchTag). In Promise code, instanceof works because every generated client shares the same class definitions from this package.

import { isInvokeFailure, InvokeRejected } from "@forst/errors";
import { $CellTaken } from "@forst/tictactoe/main/errors";

try {
  await client.main.Move({ row: 0, col: 0 });
} catch (error) {
  if (error instanceof InvokeRejected) {
    // transport failure
  }
  if (error instanceof $CellTaken) {
    // domain error
  }
}

Domain errors (error CellTaken { … }) live in @forst/gen/<forstPackage>/errors for each project (also under @forst/gen/$errors as package namespaces).

Development

From the monorepo:

cd packages/errors
bun run build
bun test

Publishing

Release Please tags errors-v* bump package.json and jsr.json. CI publishes to npm and JSR via .github/workflows/publish-packages.yml.

Manual publish from packages/errors:

bun run build
npm publish --access public --workspaces=false
npx jsr publish

Dry run:

bun run pack:dry
npx jsr publish --dry-run

npm trusted publishing (one-time)

Before CI can publish, add a trusted publisher for @forst/errors on npmjs.com (same settings as @forst/cli):

  • Repository: forst-lang/forst
  • Workflow: publish-packages.yml
  • Environment: (none, unless you use one for other packages)

License

MIT. See LICENSE.