@apm-js-collab/code-transformer-bundler-plugins 0.1.0

A universal plugin that uses @apm-js-collab/code-transformer to instrument JavaScript code at build time

@apm-js-collab/code-transformer-bundler-plugins@0.1.0 was published on 2025-06-28. Its manifest declares 3 runtime dependencies and 4 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=16.0.0.

All @apm-js-collab/code-transformer-bundler-plugins versions · Permanent reference to 0.1.0 · Latest release

Package specifications

Version0.1.0
License declarationMIT
Published2025-06-28T13:23:13.790Z
Node.js requirement>=16.0.0
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count4
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size45.73 KiB
Published file count28
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies36
Repository stars1
Repository forks2

Install @apm-js-collab/code-transformer-bundler-plugins 0.1.0

npm install @apm-js-collab/code-transformer-bundler-plugins@0.1.0
pnpm add @apm-js-collab/code-transformer-bundler-plugins@0.1.0
yarn add @apm-js-collab/code-transformer-bundler-plugins@0.1.0

Runtime dependencies

Peer requirements

  • vite ^3.0.0 || ^4.0.0 || ^5.0.0 (optional peer)
  • rollup ^3.0.0 || ^4.0.0 (optional peer)
  • esbuild * (optional peer)
  • webpack ^4.0.0 || ^5.0.0 (optional peer)

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