@pieh/friendly-errors-webpack-plugin

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

@pieh/friendly-errors-webpack-plugin@1.7.0-chalk-2 was published on 2019-03-14. Its manifest declares 4 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.

All @pieh/friendly-errors-webpack-plugin versions · Permanent reference to 1.7.0-chalk-2

Package specifications

Version1.7.0-chalk-2
License declarationMIT
Published2019-03-14T19:49:24.873Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size21.25 KiB
Published file count17
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies15
Repository stars0
Repository forks0

Install @pieh/friendly-errors-webpack-plugin 1.7.0-chalk-2

npm install @pieh/friendly-errors-webpack-plugin@1.7.0-chalk-2
pnpm add @pieh/friendly-errors-webpack-plugin@1.7.0-chalk-2
yarn add @pieh/friendly-errors-webpack-plugin@1.7.0-chalk-2

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.

Binary-Artifacts10/10 — no binaries found in the repo
SAST0/10 — no SAST tool detected
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review0/10 — Found 0/30 approved changesets -- 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
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness