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

@docxkit/errors

v0.8.0

Published

Shared error class and error codes for docx-kit packages

Readme

@docxkit/errors

Shared errors backed by a silent, typed Nostics catalog. Generation and browser preview share the same DocxKitError class without depending on each other. Nostics is pinned to 1.3.0 and no reporters are enabled.

import {
  createDocxKitError,
  DIAGNOSTIC_CODES,
  DocxKitError,
  ERROR_CODES,
  serializeDocxKitError,
} from '@docxkit/errors'

const cause = new Error('Original failure')
const error = createDocxKitError('PLUGIN_NOT_REGISTERED', {
  pluginName: 'qrcode',
}, { cause })

error instanceof DocxKitError // true
error.code === ERROR_CODES.PLUGIN_NOT_REGISTERED // true
error.diagnosticCode === DIAGNOSTIC_CODES.PLUGIN_NOT_REGISTERED // true
console.error(serializeDocxKitError(error))

// Existing three-argument construction and custom codes still work.
const custom = new DocxKitError('CUSTOM_CODE', 'Custom failure', cause)

createDocxKitError(code, params, options?) infers parameters from the code. options.cause preserves the original value; options.message retains a legacy message when needed. Known errors expose diagnosticCode, fix, and docs. Unknown custom codes do not acquire a diagnostic code or a documentation URL. The optional fourth constructor argument accepts explicit fix, docs, and sources.

serializeDocxKitError(error) emits only code, diagnosticCode, message, fix, and docs for known errors, or a readable message for other exceptions. It omits stack traces, causes, source locations, and document data. For HTTP(S), WebSocket, FTP, and file URLs, usernames/passwords, query strings, and fragments are removed from all DTO text fields; malformed URL-shaped tokens are replaced with [REDACTED URL]. This leaves the original error and its message unchanged. Unconvertible thrown values produce Unknown error. Other free-form content is preserved, so avoid embedding document content or standalone secrets in messages intended for display.

@docxkit/core and both docx-kit platform entries re-export these APIs and their types. Document, style, and plugin types remain in the declaration-only @docxkit/types package.

See the error reference for all 18 codes and repairs. To update the reference, edit the runtime catalog and docs/errors/_meta/, then run pnpm docs:errors:generate. pnpm docs:errors:check detects missing, outdated, and unexpected pages without modifying files, and runs as part of pnpm docs:verify.