acorn-numeric-separator

Support for numeric separators in acorn

acorn-numeric-separator@0.3.6 was published on 2020-08-13. Its manifest declares 0 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.8.2.

Deprecated: acorn>=7.4 supports numeric separators

All acorn-numeric-separator versions · Permanent reference to 0.3.6

Package specifications

Version0.3.6
License declarationMIT
Published2020-08-13T08:03:07.469Z
Node.js requirement>=4.8.2
Type declarationsNot declared
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size65.48 KiB
Published file count19
Package typeNot declared
ES module entrydist/acorn-numeric-separator.mjs
Default entrydist/acorn-numeric-separator.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars7
Repository forks2

Install acorn-numeric-separator 0.3.6

npm install acorn-numeric-separator@0.3.6
pnpm add acorn-numeric-separator@0.3.6
yarn add acorn-numeric-separator@0.3.6

Runtime dependencies

  • None declared

Peer requirements

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-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    Maintained0/10 — project is archived
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness