npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-plugin-ocavue

v0.3.0

Published

Custom ESLint rules from ocavue

Readme

eslint-plugin-ocavue

NPM version

Custom ESLint rules from ocavue.

Usage

Requires ESLint 10 with flat config.

pnpm add -D eslint-plugin-ocavue
// eslint.config.js
import ocavue from 'eslint-plugin-ocavue'

export default [
  {
    plugins: { ocavue },
    rules: {
      'ocavue/no-implicit-arrow-linebreak': 'error',
      'ocavue/prefer-constant-function': 'error',
      'ocavue/prefer-noop': 'error',
      'ocavue/prefer-sleep': 'error',
      'ocavue/prefer-while-true': 'error',
    },
  },
]

Rules

no-implicit-arrow-linebreak

Disallow a linebreak between => and an implicit arrow function body. Unlike @stylistic/implicit-arrow-linebreak, whose fixer joins the two lines into one (which Prettier then breaks again whenever the joined line exceeds printWidth, so eslint --fix and the formatter never converge), this rule's fixer converts the body to a block body with return. A block body is a stable shape for Prettier and oxfmt, so one round of eslint --fix plus the formatter converges.

// Incorrect
const items = Array.from({ length: count }, (_, index) => {
  return createItem(index === 0 ? 'first item label' : `item number ${index}`)
})

// Correct
const short = (index) => createItem(`item number ${index}`)

// Correct (what the fixer produces, after formatting)
const items = Array.from({ length: count }, (_, index) => {
  return createItem(index === 0 ? 'first item label' : `item number ${index}`)
})

When a comment sits between => and the body, the rule reports without autofixing so the fix never drops a comment.

prefer-constant-function

Enforce returnTrue, returnFalse and returnNull from @ocavue/utils instead of inline functions such as () => true, () => false and () => null.

// Incorrect
const all = items.filter(() => true)

// Correct (what the suggestion produces)
import { returnTrue } from '@ocavue/utils'

const all = items.filter(returnTrue)

The rule offers an editor suggestion, not an autofix. returnFalse returns the literal type false, while TypeScript infers () => false as () => boolean, so the swap can narrow an inferred type:

const [open, setOpen] = useState(() => false) // open: boolean
const [open, setOpen] = useState(returnFalse) // open: false, so setOpen(true) is a type error

The rule uses the same checkDependency option, skip conditions and import handling as prefer-noop.

prefer-noop

Enforce noop from @ocavue/utils instead of inline empty functions such as () => {}, () => undefined and function () {}. A shared noop reads as intent ("do nothing on purpose") and avoids creating a new function on every render or call.

// Incorrect
;<button onClick={() => {}} />

// Correct (what the fixer produces)
import { noop } from '@ocavue/utils'

;<button onClick={noop} />

The rule only runs when the nearest package.json of the linted file lists @ocavue/utils in dependencies, devDependencies or peerDependencies, or when the file already imports @ocavue/utils. Set checkDependency: false to run it in every file:

export default [
  {
    rules: {
      'ocavue/prefer-noop': ['error', { checkDependency: false }],
    },
  },
]

The rule skips functions where the swap could change runtime behavior: async functions, generators, named function expressions, methods, and functions with default values or destructuring in their parameters.

The fixer adds noop to an existing import { ... } from '@ocavue/utils', or adds a new import. It reports without autofixing when the function holds a comment, when another binding named noop is in scope, or when the file is not an ES module.

prefer-sleep

Enforce sleep from @ocavue/utils instead of a new Promise that only resolves after setTimeout.

// Incorrect
await new Promise((resolve) => setTimeout(resolve, 100))
await new Promise((resolve) => setTimeout(() => resolve(), 100))

// Correct (what the fixer produces)
import { sleep } from '@ocavue/utils'

await sleep(100)

The rule also matches globalThis.setTimeout and window.setTimeout, block bodies, and new Promise<void> in TypeScript. It skips promises that resolve with a value, pass extra arguments to setTimeout, or compute the delay from the executor's parameters.

The rule uses the same checkDependency option and import handling as prefer-noop.

prefer-while-true

Enforce while (true) instead of for (;;) for infinite loops. Rules such as no-constant-condition (with checkLoops: "all") and @typescript-eslint/no-unnecessary-condition report while (true) but not for (;;), so people often rewrite the loop as for (;;) to silence them. That only hides the infinite loop from the linter: the code still loops forever. This rule removes that workaround. while (true) also reads more clearly than for (;;).

// Incorrect
while (true) {
  step()
}

// Correct (what the fixer produces)
while (true) {
  step()
}

When a comment sits inside the loop head, the rule reports without autofixing so the fix never drops a comment.

Sponsors

License

MIT © ocavue