eslint-plugin-pnpm-catalog

ESLint plugin that enforces the use of named catalogs in pnpm workspaces. Automatically migrates plain dependency specifiers to catalog references and organizes them into categorized catalogs.

Features

• 🔧 Automatic migration: Converts plain version specifiers to catalog references
• 📦 Smart categorization: Automatically categorizes dependencies into appropriate catalogs (e.g., frontend, dev, testing)
• 🎯 Custom rules: Define your own categorization rules with regex patterns or exact matches
• ⚡ Conflict resolution: Handles version conflicts with configurable strategies
• 🛠️ Auto-fix: Automatically updates both package.json and pnpm-workspace.yaml

Installation

pnpm install --save-dev eslint-plugin-pnpm-catalog

Usage

Add the plugin to your ESLint config (Flat Config):

import eslintCatalogPlugin from 'eslint-plugin-pnpm-catalog'

export default [
  {
    files: ['package.json'],
    plugins: {
      'pnpm-catalog': eslintCatalogPlugin,
    },
    rules: {
      'pnpm-catalog/json-enforce-named-catalogs': 'warn',
    },
  },
]

Or use the recommended configuration:

import eslintCatalogPlugin from 'eslint-plugin-pnpm-catalog'

export default [
  eslintCatalogPlugin.configs.recommended,
]

Rules

json-enforce-named-catalogs

Enforces the use of named catalogs instead of plain version specifiers in package.json files. This rule helps maintain consistency across your workspace by organizing dependencies into logical catalogs.

Options

{
  allowedProtocols?: string[]          // Default: ['workspace', 'link', 'file']
  autofix?: boolean                    // Default: true
  conflicts?: 'new-catalog' | 'overrides' | 'error'  // Default: 'new-catalog'
  fields?: string[]                    // Default: ['dependencies', 'devDependencies']
  customRules?: CatalogRule[]          // Default: []
}

allowedProtocols

Array of protocol prefixes that should not be converted to catalogs (e.g., workspace:, link:, file:).

autofix

Whether to automatically fix violations by updating both package.json and pnpm-workspace.yaml.

conflicts

Strategy for handling version conflicts when adding packages to existing catalogs:

• new-catalog: Create a new catalog for conflicting versions
• overrides: Override the existing catalog entry
• error: Report an error without fixing

fields

Array of package.json fields to check for dependencies.

customRules

Array of custom categorization rules:

interface CatalogRule {
  name: string // Catalog name
  match: string | string[] // Package name patterns (supports regex)
  depFields?: string[] // Dependency fields this rule applies to
  priority?: number // Rule priority (higher = more important)
}

Examples

Basic usage:

// package.json (before)
{
  "dependencies": {
    "react": "^18.0.0",
    "vue": "^3.5.0"
  },
  "devDependencies": {
    "@types/node": "^20.0.0"
  }
}

// package.json (after)
{
  "dependencies": {
    "react": "catalog:frontend",
    "vue": "catalog:frontend"
  },
  "devDependencies": {
    "@types/node": "catalog:dev"
  }
}

# pnpm-workspace.yaml (updated)
catalogs:
  frontend:
    react: ^18.0.0
    vue: ^3.5.0
  dev:
    '@types/node': ^20.0.0

With custom rules:

{
  "rules": {
    "pnpm-catalog/json-enforce-named-catalogs": ["warn", {
      "customRules": [
        {
          "name": "ui-components",
          "match": ["@mui/*", "@chakra-ui/*", "antd"],
          "priority": 100
        },
        {
          "name": "testing",
          "match": "^(vitest|jest|@testing-library/)",
          "depFields": ["devDependencies"],
          "priority": 90
        }
      ]
    }]
  }
}

Conflict handling:

{
  "rules": {
    "pnpm-catalog/json-enforce-named-catalogs": ["warn", {
      "conflicts": "new-catalog" // Creates new catalogs for conflicts
    }]
  }
}

Acknowledgments

This work has been inspired by the work of pncat.

Also special thanks to Anthony Fu for:

• His work on pnpm-workspace-utils which provided the foundation for this plugin.
• His article Categorizing Dependencies which provided great inspiration.

License

MIT License © onmax