@openagenda/verror
richer JavaScript errors
@openagenda/verror@3.2.0 was published on 2026-02-09. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All @openagenda/verror versions · Permanent reference to 3.2.0 · View npm registry JSON
Package specifications
| Version | 3.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2026-02-09T09:22:34.943Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 93.71 KiB |
| Published file count | 21 |
| Package type | Not declared |
| ES module entry | dist/index.mjs |
| Default entry | index.js |
| Side effects declaration | false |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @openagenda/verror 3.2.0
npm install @openagenda/verror@3.2.0 pnpm add @openagenda/verror@3.2.0 yarn add @openagenda/verror@3.2.0
Runtime dependencies
- assertion-error ^1.1.0
- depd ^2.0.0
- inherits ^2.0.4
- sprintf-js ^1.1.2
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- assertion-error@1.1.0 — direct
- depd@2.0.0 — direct
- inherits@2.0.4 — direct
- sprintf-js@1.1.3 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-01T14:26:39.789Z
- https://api.deps.dev/v3/systems/npm/packages/%40openagenda%2Fverror/versions/3.2.0 — retrieved 2026-11-01T14:26:40.212Z
- https://api.deps.dev/v3/systems/npm/packages/%40openagenda%2Fverror/versions/3.2.0:dependencies — retrieved 2026-11-01T14:26:40.239Z