clean-write
Cleanup corrupted files on write errors
clean-write@0.0.1 was published on 2019-08-08. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.12.0.
Deprecated: Please use write-file-atomic instead
All clean-write versions ยท Permanent reference to 0.0.1
Package specifications
| Version | 0.0.1 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2019-08-08T14:46:13.602Z |
| Node.js requirement | >=8.12.0 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 17.87 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | build/src/main.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install clean-write 0.0.1
npm install clean-write@0.0.1 pnpm add clean-write@0.0.1 yarn add clean-write@0.0.1
Runtime dependencies
- core-js ^3.1.4
- path-exists ^4.0.0
- signal-exit ^3.0.2
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/clean-write/0.0.1 โ retrieved 2026-11-01T07:27:40.483Z