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

@yasainet/eslint

v0.0.39

Published

ESLint

Readme

@yasainet/eslint

Shared ESLint configuration for Next.js, Node.js and Deno.

Entry Points

| Entry | Feature Root | Entry Points | Description | | ----------------------- | ------------------------------ | ----------------------- | ----------------------------- | | @yasainet/eslint/next | src/features/ | - | Common rules + Next.js | | @yasainet/eslint/node | scripts/features/ | scripts/commands/*.ts | Common rules (CLI scripts) | | @yasainet/eslint/deno | supabase/functions/features/ | - | Common rules (Edge Functions) |

Directory Structure

src/
├── common/   # Shared rules for all environments
├── next/     # Next.js-specific rules (hooks, components, directives)
├── node/     # Node.js CLI scripts (scripts/features, scripts/commands)
└── deno/     # Deno entry point (entry-point boundary, _utils boundary, _lib boundary)

Each entry point enforces a feature-based architecture with the following convention in consuming projects:

{featureRoot}/
├── {feature}/
│   ├── actions/        # *.action.ts — entry points (handleXxx)
│   ├── services/       # *.service.ts — business logic
│   ├── repositories/   # *.repo.ts — data access
│   ├── types/          # *.type.ts
│   ├── schemas/        # *.schema.ts
│   ├── utils/          # *.util.ts
│   └── constants/      # *.constant.ts
├── shared/             # Cross-feature shared modules
├── ...
{libRoot}/              # *.lib.ts — library wrappers (e.g., supabase.lib.ts)
{utilsRoot}/            # *.util.ts — top-level utilities

Setup

Next.js + Node.js + Deno

npm install -D @yasainet/eslint
// eslint.config.mjs
import { eslintConfig as nextEslintConfig } from "@yasainet/eslint/next";
import { eslintConfig as nodeEslintConfig } from "@yasainet/eslint/node";
import { eslintConfig as denoEslintConfig } from "@yasainet/eslint/deno";
import { defineConfig, globalIgnores } from "eslint/config";
import nextVitals from "eslint-config-next/core-web-vitals";
import nextTs from "eslint-config-next/typescript";

export default defineConfig([
  ...nextVitals,
  ...nextTs,
  // Override default ignores of eslint-config-next.
  globalIgnores([
    // Default ignores of eslint-config-next:
    ".next/**",
    ".vercel/**",
    "out/**",
    "build/**",
    "next-env.d.ts",
  ]),
  ...nextEslintConfig,
  ...nodeEslintConfig,
  ...denoEslintConfig,
]);

Next.js

npm install -D @yasainet/eslint
// eslint.config.mjs
import { eslintConfig } from "@yasainet/eslint/next";
import { defineConfig, globalIgnores } from "eslint/config";
import nextVitals from "eslint-config-next/core-web-vitals";
import nextTs from "eslint-config-next/typescript";

export default defineConfig([
  ...nextVitals,
  ...nextTs,
  // Override default ignores of eslint-config-next.
  globalIgnores([
    // Default ignores of eslint-config-next:
    ".next/**",
    ".vercel/**",
    "out/**",
    "build/**",
    "next-env.d.ts",
  ]),
  ...eslintConfig,
]);

Node.js

npm install -D @yasainet/eslint eslint typescript-eslint
// eslint.config.mjs
import { eslintConfig } from "@yasainet/eslint/node";

export default [...eslintConfig];

Deno

npm install -D @yasainet/eslint eslint typescript-eslint
// eslint.config.mjs
import { eslintConfig } from "@yasainet/eslint/deno";

export default [...eslintConfig];

Release

Version is derived from the Git tag. CI automatically sets package.json version before publishing.

  1. Commit and push to main
  2. Create and push a tag:
git tag v1.0.0
git push --tags
  1. GitHub Actions will automatically publish to npm