write 2.0.0
Write data to a file, replacing the file if it already exists and creating any intermediate directories if they don't already exist. Thin wrapper around node's native fs methods.
write@2.0.0 was published on 2019-09-04. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.
All write versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-09-04T06:51:25.005Z |
| Node.js requirement | >=10 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | 4.50 KiB |
| Minified + gzip | 1.79 KiB |
| Unpacked distribution size | 18.77 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 82 |
| Repository forks | 8 |
Install write 2.0.0
npm install write@2.0.0 pnpm add write@2.0.0 yarn add write@2.0.0
Runtime dependencies
- add-filename-increment ^1.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- add-filename-increment@1.0.0 — direct
- strip-filename-increment@2.0.1 — indirect
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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Code-Review | 1/10 — Found 2/20 approved changesets -- score normalized to 1 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/write/2.0.0 — retrieved 2026-10-29T08:28:28.211Z
- https://api.deps.dev/v3/systems/npm/packages/write/versions/2.0.0:dependencies — retrieved 2026-10-29T07:46:46.774Z
- https://bundlephobia.com/api/size?package=write%402.0.0 — retrieved 2026-10-29T07:46:46.758Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fwrite — retrieved 2026-10-29T05:58:58.353Z
- https://api.deps.dev/v3/systems/npm/packages/write/versions/2.0.0 — retrieved 2026-10-29T07:46:46.744Z (stale snapshot; refresh pending)