friendly-errors-webpack-plugin

Recognizes certain classes of webpack errors and cleans, aggregates and prioritizes them to provide a better Developer Experience

friendly-errors-webpack-plugin@1.7.0 was published on 2018-04-05. Its manifest declares 3 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All friendly-errors-webpack-plugin versions · Permanent reference to 1.7.0

Package specifications

Version1.7.0
License declarationMIT
Published2018-04-05T13:04:26.415Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size24.91 KiB
Published file count17
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies13
Repository stars740
Repository forks74

Install friendly-errors-webpack-plugin 1.7.0

npm install friendly-errors-webpack-plugin@1.7.0
pnpm add friendly-errors-webpack-plugin@1.7.0
yarn add friendly-errors-webpack-plugin@1.7.0

Runtime dependencies

Peer requirements

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.

Code-Review4/10 — Found 7/17 approved changesets -- score normalized to 4
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/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