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-config-react-native-strict

v0.2.0

Published

React Native's ESLint config with every warning promoted to an error

Readme

eslint-config-react-native-strict

ci

React Native's official ESLint config (@react-native/eslint-config) with every warn-level rule promoted to error - so your project's lint config is only ever error or off, never warn.

Why

A permanent warn is a deferred decision that rots into ignored noise:

  • If a rule matters, it should be an error - Lint fails and requires a fix.
  • If it doesn't, it should be off - explicitly, on purpose.

A warn is neither. Lint should return zero errors and zero warnings. This preset removes the middle option from React Native's defaults, leaving one decision per rule: error or off.

Install

yarn add -D eslint-config-react-native-strict

@react-native/eslint-config and eslint are peer dependencies - already present in React Native projects (>=0.72). This preset derives from whatever version of @react-native/eslint-config you have installed, so it tracks React Native upgrades automatically; there is no hand-maintained rule list.

Usage

In .eslintrc.js:

module.exports = {
  root: true,
  extends: ['react-native-strict'],
  rules: {
    // Deliberate, documented exceptions - turn rules OFF, never to warn:
    'react-native/no-inline-styles': 'off', // inline styles are fine here
    'no-bitwise': 'off', // bitwise ops are intentional
  },
};

How it works

The whole package is one pure function applied to the config you already have:

strictify(require('@react-native/eslint-config'));

It flips every warn to error - preserving each rule's options and recursing into overrides - and leaves off and error untouched. It is rule-agnostic by design: it changes only severity, never which rules exist. Deciding which rules belong in your project is your job - extend this preset for the severity policy, then turn off the ones you don't want.

Deprecated rules

Because the transform is pure, React Native's handful of deprecated ESLint rules (no-catch-shadow, no-negated-in-lhs, no-mixed-requires, no-new-require, no-path-concat, no-restricted-modules, handle-callback-err) are promoted to error too. Turn them off like other exceptions if you don't want them.

License

MIT