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

@prairielearn/trpc

v1.0.0

Published

Readme

@prairielearn/trpc

Shared tRPC infrastructure for PrairieLearn applications. Import from an explicit subpath so that browser builds cannot pull in server-only dependencies.

| Subpath | Public API | | ---------------------------- | -------------------------------------------------------------------- | | @prairielearn/trpc/server | appErrorFormatter, throwAppError, and application-error types | | @prairielearn/trpc/client | AppError, AppErrorRenderers, getAppError, and renderAppError | | @prairielearn/trpc/react | AppErrorAlert and QueryClientProviderDebug | | @prairielearn/trpc/express | isTrpcRequest, isMultipartRequest, and formatTrpcErrorResponse |

Typed error maps

The server and client intentionally resolve a whole procedure error map differently:

  • throwAppError<WholeErrorMap> accepts only variants shared by every procedure. This prevents a helper that can run for every procedure from throwing an error that some procedures did not declare.
  • getAppError<WholeErrorMap> returns the union of all procedure variants. This supports a client component that handles failures from several procedures.

For a single procedure, pass its map entry to either helper, such as throwAppError<WidgetError['Update']>(...) or getAppError<WidgetError['Update']>(error).

Express errors before the adapter

formatTrpcErrorResponse builds the SuperJSON-wrapped tRPC error response used when authentication, authorization, CSRF, or other Express middleware fails before the tRPC adapter runs. Its numeric JSON-RPC code is sourced from tRPC's own TRPC_ERROR_CODES_BY_KEY constants.

Error IDs generated for normal Express errors and adapter errors remain server-side and correlate application logs with error reporting. The shared response shape does not expose an error ID to clients.