Is rollup-plugin-terser still maintained?
deprecated — observed 2026-08-03
As of 2026-08-03, the npm package rollup-plugin-terser is recorded deprecated: the package is marked deprecated on the npm registry. 3098 other npm packages still declare a dependency on it (npm dependency graph).
rollup-plugin-terser is recorded as deprecated in the lastseen.dev component-maintenance dataset as of 2026-08-03. Definition: the package is marked deprecated on the npm registry. At the observation, 3098 other npm packages still declared a dependency on it, which is why this dead package carries a page. Method: read from the public npm registry metadata and the cross-registry dependency graph (authoritative). This is a dated factual observation about one package, not advice about any named party.
API (npm is POST-only): curl -X POST https://lastseen.dev/api/v1/manifest -H 'Content-Type: application/json' -d '{"components":[{"name":"rollup-plugin-terser","kind":"npm"}]}' — add ?as_of=2026-08-03 for a point-in-time read. See /api/v1/docs.
- State
- deprecated — the package is marked deprecated on the npm registry
- Last version published
- 2023-06-09
- Dependents (npm)
- 3098 other packages still declare a dependency on this
- Method
- npm registry metadata + cross-registry dependency graph (authoritative)
- Source / evidence
- npmjs.com/package/rollup-plugin-terser
- Observed as of
- 2026-08-03
- Registry
- npm
Interval-censoring. Observation window ended 2026-08-03. A state transition inside an unobserved span is dated to that interval, not to a single day. The dependent count is the number of distinct packages that still declared a dependency on this package at the observation.
A dated observation, not advice. Data under CC-BY-4.0. Check every dependency in one place: check your whole organization.
When was it last updated?
The package rollup-plugin-terser carries an npm deprecation flag as of 2026-08-03. A deprecation flag is set by the maintainer on the registry; it does not remove installable versions.
What is its recorded state?
State deprecated is derived from the npm registry metadata: the package is marked deprecated on the npm registry. This is the registry-side reading, separate from the source repository.
What does that mean for projects using it?
3098 other npm packages still declare a dependency on rollup-plugin-terser as of the observation. A pinned dependency continues to resolve to the last published version of a dead package; a floating range has no newer version to resolve to. This is a dated count of dependents, not advice about any named party.
What is the observation history?
The dated read above is the record: the state, the dependent count, the source, and the observation date. A dispute re-reads the public npm registry and the dependency graph and issues a dated correction on this page.