rollup-plugin-typescript2

Seamless integration between Rollup and TypeScript. Now with errors.

rollup-plugin-typescript2@0.37.0 was published on 2026-03-29. Its manifest declares 5 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All rollup-plugin-typescript2 versions · Permanent reference to 0.37.0

Package specifications

Version0.37.0
License declarationMIT
Published2026-03-29T05:34:12.840Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4428.54 KiB
Published file count33
Package typeNot declared
ES module entrydist/rollup-plugin-typescript2.es.js
Default entrydist/rollup-plugin-typescript2.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies20
Repository stars824
Repository forks71

Install rollup-plugin-typescript2 0.37.0

npm install rollup-plugin-typescript2@0.37.0
pnpm add rollup-plugin-typescript2@0.37.0
yarn add rollup-plugin-typescript2@0.37.0

Runtime dependencies

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review5/10 — Found 17/30 approved changesets -- score normalized to 5
Binary-Artifacts10/10 — no binaries found in the repo
Maintained1/10 — 1 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
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