@rolldown/binding-darwin-arm64 1.0.0-beta.3-commit.a36bf63

Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.

@rolldown/binding-darwin-arm64@1.0.0-beta.3-commit.a36bf63 was published on 2025-02-27. Its manifest declares 0 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 @rolldown/binding-darwin-arm64 versions · Permanent reference to 1.0.0-beta.3-commit.a36bf63 · Latest release

Package specifications

Version1.0.0-beta.3-commit.a36bf63
License declarationMIT
Published2025-02-27T00:25:41.957Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size14629.57 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entryrolldown-binding.darwin-arm64.node
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars13980
Repository forks1005

Install @rolldown/binding-darwin-arm64 1.0.0-beta.3-commit.a36bf63

npm install @rolldown/binding-darwin-arm64@1.0.0-beta.3-commit.a36bf63
pnpm add @rolldown/binding-darwin-arm64@1.0.0-beta.3-commit.a36bf63
yarn add @rolldown/binding-darwin-arm64@1.0.0-beta.3-commit.a36bf63

Runtime dependencies

  • None declared

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.

    Evidence and freshness