webpack-filter-warnings-plugin

Allows you to hide certain warnings from webpack compilations

webpack-filter-warnings-plugin@1.2.1 was published on 2018-11-25. Its manifest declares 0 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 4.3 < 5.0.0 || >= 5.10.

All webpack-filter-warnings-plugin versions · Permanent reference to 1.2.1

Package specifications

Version1.2.1
License declarationMIT
Published2018-11-25T07:44:45.386Z
Node.js requirement>= 4.3 < 5.0.0 || >= 5.10
Type declarationsNot declared
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size7.73 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entrydist/cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars27
Repository forks8

Install webpack-filter-warnings-plugin 1.2.1

npm install webpack-filter-warnings-plugin@1.2.1
pnpm add webpack-filter-warnings-plugin@1.2.1
yarn add webpack-filter-warnings-plugin@1.2.1

Runtime dependencies

  • None declared

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-Review0/10 — Found 2/22 approved changesets -- score normalized to 0
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    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
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness