write-file-webpack-plugin 4.3.2

Forces webpack-dev-server to write bundle files to the file system.

write-file-webpack-plugin@4.3.2 was published on 2018-05-19. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.

All write-file-webpack-plugin versions · Permanent reference to 4.3.2 · Latest release

Package specifications

Version4.3.2
License declarationBSD-3-Clause
Published2018-05-19T09:39:26.107Z
Node.js requirement>=4
Type declarationsNot declared
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size23.53 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entry./dist/WriteFileWebpackPlugin.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies14
Repository stars521
Repository forks53

Install write-file-webpack-plugin 4.3.2

npm install write-file-webpack-plugin@4.3.2
pnpm add write-file-webpack-plugin@4.3.2
yarn add write-file-webpack-plugin@4.3.2

Runtime dependencies

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.

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-Artifacts10/10 — no binaries found in the repo
Code-Review5/10 — Found 15/30 approved changesets -- score normalized to 5
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
License9/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