no-arrowception

ESLint rule preventing arrow functions that implicitly create arrow functions

no-arrowception@1.0.0 was published on 2015-10-30. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This module has moved and is now available at @hapi/rule-no-arrowception. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

All no-arrowception versions · Permanent reference to 1.0.0

Package specifications

Version1.0.0
License declarationMIT
Published2015-10-30T20:25:07.565Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
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 entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars5
Repository forks5

Install no-arrowception 1.0.0

npm install no-arrowception@1.0.0
pnpm add no-arrowception@1.0.0
yarn add no-arrowception@1.0.0

Runtime dependencies

  • None declared

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.

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

    Evidence and freshness