Back to Explore

ljharb/es-errors

GitHub
2 watchersOpen source

Last release:

es-errors is a small JavaScript utility that caches a few built-in JS Error constructors so you can import them consistently. It is useful if you want direct access to specific error types like EvalError, RangeError, ReferenceError, SyntaxError, TypeError, and URIError.

Project status

  • The repository appears not to be actively maintained as of today (2026-06-09), with the last upstream push on 2024-03-09 and the most recent published update in early 2024.
  • Update cadence looks bursty and then stops, with multiple version updates around 2024-02-05, but no further updates since that period (over two years gap).

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.3.0

    v1.3.0 introduces additional cached JavaScript error constructors, specifically adding EvalError and URIError. The published package is updated to expose new subpath exports (es-errors/eval and es-errors/uri) and includes matching TypeScript declaration files.

    Features
  • v1.2.1

    Release v1.2.1 updates the package metadata and changelog to address a missing export entry. The code diff indicates an export path was added so consumers can import an additional module entry point.

  • v1.2.0

    Release v1.2.0 was published, but no release notes were provided by the publisher. As a result, the changes in this version are not documented here, and developers should verify the upgrade impact by reviewing the release diff and testing key workflows.

  • v1.1.0

    This release (v1.1.0) introduces a cached export for the base JavaScript Error constructor at the package root (es-errors). No release notes were provided, so the documented behavior changes come only from the changelog and the code diff.

    Features
  • v1.0.0

    v1.0.0 was published on 2024-02-03, but the publisher provided no release notes. With no documented changes, developers should treat this upgrade as potentially containing undocumented breaking or behavioral changes and verify compatibility by running tests against the new version.