eslint-plugin-no-empty-blocks

An extended version of the `no-empty` rule that adds an option to allow empty catch blocks.

eslint-plugin-no-empty-blocks@0.0.2 was published on 2015-06-07. Its manifest declares 0 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: ESLint's native no-empty rule already supports the allowEmptyCatch option.

All eslint-plugin-no-empty-blocks versions · Permanent reference to 0.0.2

Package specifications

Version0.0.2
License declarationMIT
Published2015-06-07T05:18:56.067Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars9
Repository forks2

Install eslint-plugin-no-empty-blocks 0.0.2

npm install eslint-plugin-no-empty-blocks@0.0.2
pnpm add eslint-plugin-no-empty-blocks@0.0.2
yarn add eslint-plugin-no-empty-blocks@0.0.2

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.

    Binary-Artifacts10/10 — no binaries found in the repo
    SAST0/10 — no SAST tool detected
    Code-Review0/10 — Found 0/5 approved changesets -- score normalized to 0
    Maintained0/10 — project is archived
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    License0/10 — license file not detected
    Fuzzing0/10 — project is not fuzzed
    Branch-Protection0/10 — branch protection not enabled on development/release branches

    Evidence and freshness