@ava/babel-preset-stage-4

Efficiently applies the minimum of transforms to run stage 4 code on Node.js 6, 8 and 10

@ava/babel-preset-stage-4@4.0.0 was published on 2019-08-11. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.9.4 <9 || >=10.0.0 <11 || >=12.0.0.

All @ava/babel-preset-stage-4 versions · Permanent reference to 4.0.0

Package specifications

Version4.0.0
License declarationMIT
Published2019-08-11T18:09:27.416Z
Node.js requirement>=8.9.4 <9 || >=10.0.0 <11 || >=12.0.0
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.04 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies44
Repository stars13
Repository forks6

Install @ava/babel-preset-stage-4 4.0.0

npm install @ava/babel-preset-stage-4@4.0.0
pnpm add @ava/babel-preset-stage-4@4.0.0
yarn add @ava/babel-preset-stage-4@4.0.0

Runtime dependencies

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.

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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review1/10 — Found 2/18 approved changesets -- score normalized to 1
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness