forever 0.11.1
A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever)
forever@0.11.1 was published on 2014-04-24. Its manifest declares 12 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.x.
All forever versions · Permanent reference to 0.11.1 · Latest release
Package specifications
| Version | 0.11.1 |
|---|---|
| License declaration | Not declared |
| Published | 2014-04-24T17:11:17.861Z |
| Node.js requirement | >= 0.8.x |
| Type declarations | Not declared |
| Runtime dependency count | 12 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/forever |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install forever 0.11.1
npm install forever@0.11.1 pnpm add forever@0.11.1 yarn add forever@0.11.1
Runtime dependencies
Peer requirements
- None declared
Optional dependencies
- None declared
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
- https://registry.npmjs.org/forever/0.11.1 — retrieved 2026-10-31T19:25:22.424Z