ESLint Migration Guides
Move env and globals from legacy config into the flat config languageOptions object.
Start here
Move env settings to languageOptions.globals using the globals package, and move globals directly into languageOptions.globals.
Stop before automation when: Dynamic env selection based on file patterns. Overlapping globals from multiple sources.
const globals = require("globals");
module.exports = [{
languageOptions: {
globals: {
...globals.browser,
...globals.node,
myGlobal: "readonly",
},
},
}];
Repo fit check
Run the matching scanner locally first. The fit-report add-on is not listed for this proof-only product yet, so use the proof page and scanner output before treating it as a purchase candidate.
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewableWhy this page exists
env and globals move into languageOptions in flat config.
Direct answer
Move env settings to languageOptions.globals using the globals package, and move globals directly into languageOptions.globals.
Example
{
"env": {"browser": true, "node": true},
"globals": {"myGlobal": "readonly"}
}
const globals = require("globals");
module.exports = [{
languageOptions: {
globals: {
...globals.browser,
...globals.node,
myGlobal: "readonly",
},
},
}];
Decision path
This product exists for the static-config subset. It does not pretend to evaluate JS config logic.
Before checkout
Current listed price is not published on the pricing page yet.
Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.
FAQ
Move env settings to languageOptions.globals using the globals package, and move globals directly into languageOptions.globals.
Automate only the supported subset: Static env configuration mapping to globals package imports. Custom globals migration to languageOptions.globals. Integration with FlatCompat bridge generation. Keep these cases in manual review: Dynamic env selection based on file patterns. Overlapping globals from multiple sources. Repos with JS-backed legacy config logic.
Use ESLint Flat Config Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Run the public scan or read the proof first. The fit-report add-on is not listed for this proof-only product yet; if unsupported findings dominate, keep the work manual.
Migrate .eslintrc to eslint.config.cjs with FlatCompat, Migrate package.json eslintConfig to flat config, Why .eslintrc.js is a manual-review case, Move .eslintignore patterns into flat config, Why negated ignore patterns need manual review, Why multiple legacy ESLint config sources block flat config migration, What to do when eslint.config.* already exists, Migrate overrides to flat config arrays