run-time-assertions 0.0.1
Type safe assertions that work just as well in production run-times as they do in testing.
run-time-assertions@0.0.1 was published on 2023-09-20. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: Use @augment-vir/assert instead.
All run-time-assertions versions · Permanent reference to 0.0.1 · Latest release
Package specifications
| Version | 0.0.1 |
|---|---|
| License declaration | (MIT or CC0 1.0) |
| Published | 2023-09-20T00:15:58.794Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 17.77 KiB |
| Published file count | 13 |
| Package type | Not declared |
| ES module entry | dist/esm/index.js |
| Default entry | dist/cjs/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install run-time-assertions 0.0.1
npm install run-time-assertions@0.0.1 pnpm add run-time-assertions@0.0.1 yarn add run-time-assertions@0.0.1
Runtime dependencies
- type-fest ^4.3.1
- @augment-vir/common ^18.2.0
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.
- @augment-vir/common@18.2.0 — direct
- type-fest@4.41.0 — 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
- https://registry.npmjs.org/run-time-assertions/0.0.1 — retrieved 2026-10-31T10:26:48.970Z
- https://api.deps.dev/v3/systems/npm/packages/run-time-assertions/versions/0.0.1 — retrieved 2026-10-31T10:26:49.383Z
- https://api.deps.dev/v3/systems/npm/packages/run-time-assertions/versions/0.0.1:dependencies — retrieved 2026-10-31T10:26:49.548Z