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-next-compat

v1.0.0-alpha.4

Published

ESLint plugin for browser compatibility checking in Next.js App Router client components

Downloads

418

Readme

eslint-plugin-next-compat

English | 한국어

ESLint plugin that automatically detects client components only in Next.js App Router projects and checks browser compatibility.

This plugin uses eslint-plugin-compat internally and wraps its rules.

demo

Why Use This?

In Next.js App Router, server and client components coexist. Browser compatibility checks are only needed for client components, but existing tools can't distinguish between them.

This plugin detects client components and tracks all their dependencies, ensuring complete coverage of client-side code.

Client Code Detection

Note When tracking dependency files with barrel index patterns, server-side files may also be included in lint checks.

This plugin identifies client code based on the following criteria:

  1. Scans all .tsx, .jsx component files in src/app/** or app/** directories
  2. Identifies files with 'use client' directive
  3. Analyzes dependency tree of those files
  4. Applies eslint-plugin-compat rules to identified client files

Installation

Requirements ESLint 9+ (Flat Config only)

npm install eslint-plugin-next-compat --save-dev
# or
pnpm add -D eslint-plugin-next-compat

Usage

Note Client files are detected when ESLint starts. If you add or remove client components, restart your ESLint server (or IDE) to detect the changes.

Basic

// eslint.config.js
import nextCompat from 'eslint-plugin-next-compat';

export default [
  ...nextCompat.configs.recommended,
];

With Options

// eslint.config.js
import nextCompat from 'eslint-plugin-next-compat';

export default [
  ...nextCompat.configs.recommended({
    include: ['src/hooks/**', 'src/utils/client/**'],
    exclude: ['**/*.test.ts', '**/legacy/**'],
  }),
];

| Option | Type | Description | |--------|------|-------------| | include | string[] | Additional glob patterns to check | | exclude | string[] | Glob patterns to exclude from checking |

Strict Mode

Use error instead of warn.

export default [
  ...nextCompat.configs.strict,
];

Target Browsers

Configure via .browserslistrc or browserslist field in package.json.

If neither .browserslistrc nor the browserslist field in package.json exists, the plugin automatically detects the Next.js version and uses its required browser versions as the baseline.

# .browserslistrc
last 2 versions
not dead
not ie 11

Polyfills

Exclude APIs that are already polyfilled.

// eslint.config.js
export default [
  ...nextCompat.configs.recommended,
  {
    settings: {
      polyfills: ['fetch', 'Promise', 'IntersectionObserver'],
    },
  },
];

License

MIT