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

@ilyasso/eslint-config

v0.1.4

Published

Custom ESLint configuration for Nuxt

Readme

@ilyasso/eslint-config

Opinionated ESLint configuration for TypeScript, Vue, and Nuxt projects

A strict and opinionated ESLint configuration built on top of @antfu/eslint-config. The goal of this configuration is to provide a specific set of rules and conventions that are tailored to the needs of TypeScript projects with Vue 3, Nuxt, and modern tooling.

Features

  • TypeScript-first - Opt-in type checking with TypeScript
  • Vue and Nuxt - Vue 3 optimized, script setup api, Nuxt-specific rules and conventions
  • Import enforcement - Enforces ~/ and ~~/ aliases over relative ../ paths or @/ paths
  • Unicorn rules - All eslint-plugin-unicorn rules with sensible overrides
  • Security-first - Anti-trojan-source and secret-detection baseline; opt-in eslint-plugin-security for ReDoS, unsafe fs paths, and child_process detection
  • Code quality - eslint-plugin-sonarjs and eslint-plugin-promise bundled for complexity, duplicated-branch, and async-correctness checks
  • Flexible overrides - Easy rule customization with rules and overrides options
  • Prettier-compatible - Stylistic rules disabled, use Prettier for formatting
  • Drizzle ORM - database safety rules (require WHERE clauses)
  • Tailwind CSS - opt-in eslint-plugin-better-tailwindcss (class order, duplicate/conflicting/unknown classes, deprecated utilities)
  • Repo hygiene - eslint-plugin-depend (flags deprecated deps) and eslint-plugin-check-file (kebab-case folders) always on; eslint-plugin-package-json behind a flag

Installation

Using Bun (recommended)

bun add -D @ilyasso/eslint-config eslint typescript

Using pnpm

pnpm add -D @ilyasso/eslint-config eslint typescript

Using npm

npm install -D @ilyasso/eslint-config eslint typescript

Quick Start

Basic Usage

Create an eslint.config.ts (or .js) file in your project root:

import ilyasso from "@ilyasso/eslint-config";

export default ilyasso();

Advanced Configuration

Configuration Options

The ilyasso() function accepts an options object with the following properties:

interface IlyassoOptions {
  /**
   * TypeScript type-checking configuration
   */
  typecheck?: {
    /**
     * Enable TypeScript type-checking rules
     * @default false
     */
    enable: boolean;
    /**
     * Path to TypeScript project configuration file
     * @default './tsconfig.json'
     */
    tsconfig?: string;
  };

  /**
   * Enable strict mode, some rules may slow you down
   * @default false
   */
  strict?: boolean;

  /**
   * Enable Drizzle ORM linting rules
   * @default false
   */
  drizzle?: boolean;

  /**
   * Enable `eslint-plugin-better-tailwindcss` (class order, duplicate/conflicting/
   * unknown classes, deprecated utilities, etc.).
   * Pass `true` for auto-detection, or an object to point the plugin at your
   * Tailwind v4 CSS entry (`entryPoint`) or v3 config (`tailwindConfig`).
   * @default false
   */
  tailwind?:
    | boolean
    | {
        entryPoint?: string;
        tailwindConfig?: string;
        files?: string[];
      };

  /**
   * Enable eslint-plugin-security rules (ReDoS, non-literal fs paths,
   * child_process, eval, timing attacks, etc.). Noisy on some codebases.
   * @default false
   */
  security?: boolean;

  /**
   * Enable eslint-plugin-package-json rules on `package.json` files
   * (required fields, field order, valid SPDX, sorted deps, etc.).
   * @default false
   */
  packageJson?: boolean;

  /**
   * Files and directories to ignore
   * @default []
   */
  ignores?: string[];

  /**
   * Override or add specific ESLint rules
   * Applied as the final config, giving it highest priority
   */
  rules?: TypedFlatConfigItem["rules"];

  /**
   * Additional config objects for advanced customization
   * Can be a single config object or an array of config objects
   */
  overrides?: TypedFlatConfigItem | TypedFlatConfigItem[];

  /**
   * Additional options to pass to @antfu/eslint-config
   * (e.g., vue, typescript, markdown, etc.)
   */
  [key: string]: unknown;
}

Configuration Examples

Using the rules option to override or disable rules:

import ilyasso from "@ilyasso/eslint-config";

export default ilyasso({
  rules: {
    // Disable console warnings in development
    "no-console": "off",

    // Enforce multi-word component names
    "vue/multi-word-component-names": "error",

    // Allow magic numbers in specific cases
    "no-magic-numbers": ["warn", { ignore: [-1, 0, 1, 2, 10, 100] }],
  },
});

Using the overrides option for file-specific rules:

import ilyasso from "@ilyasso/eslint-config";

export default ilyasso({
  overrides: {
    files: ["*.test.ts", "*.spec.ts"],
    rules: {
      "no-magic-numbers": "off",
      "no-console": "off",
    },
  },
});

Multiple Override Configs

You can pass an array of override configs for different file patterns:

import ilyasso from "@ilyasso/eslint-config";

export default ilyasso({
  overrides: [
    {
      files: ["*.test.ts", "*.spec.ts"],
      rules: {
        "no-magic-numbers": "off",
        "no-console": "off",
      },
    },
    {
      files: ["scripts/**/*.ts"],
      rules: {
        "no-console": "off",
        "node/prefer-global/process": "off",
      },
    },
    {
      files: ["*.config.ts", "*.config.js"],
      rules: {
        "no-magic-numbers": "off",
      },
    },
  ],
});

Tailwind CSS

Enable eslint-plugin-better-tailwindcss and point it at your Tailwind config so the plugin can resolve your custom theme:

import ilyasso from "@ilyasso/eslint-config";

// Tailwind v4 (CSS-first config)
export default ilyasso({
  tailwind: { entryPoint: "app/assets/css/main.css" },
});

// Tailwind v3 (JS config)
export default ilyasso({
  tailwind: { tailwindConfig: "tailwind.config.ts" },
});

The recommended preset enables class-order, duplicate, conflicting, deprecated, and unknown-class rules. Stylistic rules report as warnings; correctness rules as errors. Lints **/*.vue and **/*.{ts,tsx,js,jsx} by default — pass files to override.

If you also use prettier-plugin-tailwindcss, disable better-tailwindcss/enforce-consistent-class-order via the rules option to avoid the two formatters fighting over class order.

TypeScript Type Checking with Nuxt

If you want to enable type checking rules in a Nuxt project, you'll need to create a custom tsconfig.eslint.json file. This is required because Nuxt generates its TypeScript configuration dynamically.

Create a tsconfig.eslint.json file in your project root:

{
  "extends": "./.nuxt/tsconfig.json",
  "include": ["app/**/*", "server/**/*", "shared/**/*", "*.ts", "*.vue"],
  "exclude": ["node_modules", ".nuxt", ".output", "dist"]
}

Then reference it in your ESLint configuration:

import ilyasso from "@ilyasso/eslint-config";

export default ilyasso({
  typecheck: {
    enable: true,
    tsconfig: "./tsconfig.eslint.json",
  },
});

Requirements

  • TypeScript >= 5.0.0 (required)
  • ESLint >= 9.0.0 (required)
  • Node.js >= 24.0.0 (recommended)

Note: This package is designed for TypeScript projects only. JavaScript projects are not supported.

File scope conventions

This config is tailored for Nuxt projects. A few rule groups only apply to Nuxt-specific directories:

  • Node rules (node/no-sync, node/no-process-env, node/prefer-global/*, etc.) apply only to files under server/**/*.ts and shared/**/*.ts — the Nuxt/Nitro convention. If your project uses a different layout (e.g., src/server/), these rules will not fire; use the overrides option to broaden the scope.
  • Vue rules apply to **/*.vue only.
  • Markdown rules apply to **/*.md and fenced code blocks inside markdown.

Strict mode

strict: true upgrades selected rules from warn to error (notably no-console, no-magic-numbers, no-param-reassign, no-await-in-loop, ts/ban-ts-comment) and enforces interface over type for type definitions. Use it when you want the config to block commits rather than just flag problems.

Recommended Setup

With Prettier

This config disables all stylistic rules to avoid conflicts with Prettier. Install Prettier separately:

bun add -D prettier

Package Scripts

Add these scripts to your package.json:

{
  "scripts": {
    "lint": "eslint",
    "lint:fix": "eslint --fix",
    "format": "prettier --write .",
    "format:check": "prettier --check ."
  }
}

License

MIT © 2025 Ilyas Turki

Credits

Built on top of @antfu/eslint-config by Anthony Fu.

Contributing

Issues and pull requests are welcome! This is a personal configuration but feedback is appreciated.