Build ESLint configuration files with rule selection, plugin setup, and environment targeting.
Rule choices, plugin declarations, and runtime targets are assembled into an ESLint configuration that can be reviewed and copied into a project. The generator is useful when you know the linting policy you want but do not want to compose every configuration entry by hand. The frequent surprise is that naming a plugin in a configuration does not install that plugin or guarantee its rules exist in the installed version. Also verify whether the generated syntax is flat configuration or the older eslintrc form before using it.
A selected core or plugin rule is written as a rule key paired with a severity. ESLint accepts severity names or numeric equivalents, and rules with options use an array whose first item is the severity. The generated entry controls only files reached by its configuration block, so configuration placement, ignores, and file matching can still change which source files are checked.
Plugin setup identifies additional rule namespaces, while environment targeting describes expected runtime globals and language context. These choices do not install packages, execute ESLint, transpile source code, or add runtime compatibility. Flat configuration and eslintrc represent plugins and environments differently, so treat the generated structure as belonging to one configuration system rather than as syntax that can be moved unchanged between both.
Not necessarily. Core ESLint rules need no separate rule package, but plugin rules require the corresponding plugin to be available to the project and referenced in the form expected by its configuration system. The generator produces configuration text; it does not add npm dependencies, reconcile plugin versions, or verify the project's existing package installation.
No. An environment choice helps ESLint interpret runtime-specific globals and related configuration context. It does not rewrite syntax, provide missing APIs, create polyfills, or test actual runtime support. Compatibility remains a separate concern involving the project's target versions, build process, dependencies, and runtime testing.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.