Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/antfu/eslint-flat-config-utils below:

antfu/eslint-flat-config-utils: Utils for managing and manipulating ESLint flat config arrays

Utils for managing and manipulating ESLint flat config arrays

Documentation

npm i eslint-flat-config-utils

Most of the descriptions are written in JSDoc, you can find more details in the documentation via JSR.

Here listing a few highlighted ones:

Concatenate multiple ESLint flat configs into one, resolve the promises, and flatten the array.

// eslint.config.mjs
import { concat } from 'eslint-flat-config-utils'

export default concat(
  {
    plugins: {},
    rules: {},
  },
  // It can also takes a array of configs:
  [
    {
      plugins: {},
      rules: {},
    }
    // ...
  ],
  // Or promises:
  Promise.resolve({
    files: ['*.ts'],
    rules: {},
  })
  // ...
)

Create a chainable composer that makes manipulating ESLint flat config easier.

It extends Promise, so that you can directly await or export it to eslint.config.mjs

// eslint.config.mjs
import { composer } from 'eslint-flat-config-utils'

export default composer(
  {
    plugins: {},
    rules: {},
  }
  // ...some configs, accepts same arguments as `concat`
)
  .append(
    // appends more configs at the end, accepts same arguments as `concat`
  )
  .prepend(
    // prepends more configs at the beginning, accepts same arguments as `concat`
  )
  .insertAfter(
    'config-name', // specify the name of the target config, or index
    // insert more configs after the target, accepts same arguments as `concat`
  )
  .renamePlugins({
    // rename plugins
    'old-name': 'new-name',
    // for example, rename `n` from `eslint-plugin-n` to more a explicit prefix `node`
    'n': 'node'
    // applies to all plugins and rules in the configs
  })
  .override(
    'config-name', // specify the name of the target config, or index
    {
      // merge with the target config
      rules: {
        'no-console': 'off'
      },
    }
  )

// And you can directly return the composer object to `eslint.config.mjs`

This helper renames plugins in all configurations in the composer. It is useful when you want to enforce a plugin to a custom name:

const config = await composer([
  {
    plugins: {
      n: pluginN,
    },
    rules: {
      'n/foo': 'error',
    }
  }
])
  .renamePlugins({
    n: 'node'
  })

// The final config will have `node/foo` rule instead of `n/foo`

This helper removes specified rules from all configurations in the composer. It is useful when you are certain that these rules are not needed in the final configuration. Unlike overriding with off, removed rules are not affected by priority considerations.

const config = await composer([
  {
    rules: {
      'foo/bar': 'error',
      'foo/baz': 'warn',
    }
  },
  {
    files: ['*.ts'],
    rules: {
      'foo/bar': 'off',
    }
  }
  // ...
])
  .removeRules(
    'foo/bar',
    'foo/baz',
  )

// The final config will not have `foo/bar` and `foo/baz` rules at all

This helper hijack plugins to make fixable rules non-fixable, useful when you want to disable auto-fixing for some rules but still keep them enabled.

For example, if we want the rule to error when we use let on a const, but we don't want auto-fix to change it to const automatically:

const config = await composer([
  {
    plugins: {
      'unused-imports': pluginUnusedImports,
    },
    rules: {
      'perfer-const': 'error',
      'unused-imports/no-unused-imports': 'error',
    }
  }
])
  .disableRulesFix(
    [
      'prefer-const',
      'unused-imports/no-unused-imports',
    ],
    {
      // this is required only when patching core rules like `prefer-const` (rules without a plugin prefix)
      builtinRules: () => import('eslint/use-at-your-own-risk').then(r => r.builtinRules),
    },
  )

Note

This function mutate the plugin object which will affect all the references to the plugin object globally. The changes are not reversible in the current runtime.

Extend another flat config from a different root, and rewrite the glob paths accordingly:

import { extend } from 'eslint-flat-config-utils'

export default [
  ...await extend(
    import('./sub-package/eslint.config.mjs'),
    './sub-package/'
  )
]

MIT License © 2023-PRESENT Anthony Fu

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4