GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Update the ESLint section to flat config (eslint.config.js) by 1t1sCooL · Pull Request #3995 · javascript-tutorial/en.javascript.info

Conversation

@1t1sCooL

@1t1sCooL 1t1sCooL commented Sep 17, 2026

Copy link
Copy Markdown

The "Code style" chapter tells the reader to create an .eslintrc file. That format is no longer the way ESLint is configured: flat config (eslint.config.js) has been the default since ESLint 9, and .eslintrc support was removed in ESLint 10, so following the chapter today leaves beginners with a config that ESLint ignores.

This updates that part of the section:

  • install ESLint into the project (npm install --save-dev eslint) instead of globally, and mention npm init @eslint/config@latest, which generates the config;
  • replace the .eslintrc example with an equivalent eslint.config.js one (same idea: start from the recommended rules, declare browser/node globals, then override a couple of rules);
  • point the installation link at the current page, https://eslint.org/docs/latest/use/getting-started (the old docs/user-guide/getting-started URL now redirects).

The wording and the structure of the section are otherwise untouched.

Reported for the Russian translation in javascript-tutorial/ru.javascript.info#2187; fixing it here first so the change is not overwritten by the next upstream sync.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@1t1sCooL
Update the ESLint section to flat config (eslint.config.js)
c280c2f
@javascript-translate-bot javascript-translate-bot added the review needed Review needed, please approve or request changes label Sep 17, 2026
@javascript-translate-bot
javascript-translate-bot requested a review from a team September 17, 2026 16:00
@1t1sCooL 1t1sCooL mentioned this pull request Sep 17, 2026
[Предложение: учебник]: Устаревшая информация про ESLint в статье «Стиль кода» javascript-tutorial/ru.javascript.info#2187
Open
AKzar1el
AKzar1el reviewed Nov 2, 2026
View reviewed changes

@AKzar1el AKzar1el left a comment

Copy link
Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two concrete setup pitfalls in the new ESLint flat-config instructions, noted inline. This is a source/documentation review; I did not run ESLint or the repository's tests.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread 1-js/03-code-quality/02-coding-style/article.md
1. Install [Node.js](https://nodejs.org/).
2. Install ESLint with the command `npm install -g eslint` (npm is a JavaScript package installer).
3. Create a config file named `.eslintrc` in the root of your JavaScript project (in the folder that contains all your files).
2. Install ESLint in your project with the command `npm install --save-dev eslint` (npm is a JavaScript package installer).

@AKzar1el AKzar1el Nov 2, 2026

Copy link
Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The manual install command only declares eslint, but the sample at lines 322–323 imports @eslint/js and globals. Those should be explicit project dev dependencies rather than depending on how transitive packages happen to be hoisted. Could this step say npm install --save-dev eslint @eslint/js globals (and mention npm init -y first if there is no package.json)? ESLint's manual setup explicitly installs @eslint/js. The npm init @eslint/config@latest generator is an alternative path, but readers copying the manual example otherwise lack the declared dependencies.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread 1-js/03-code-quality/02-coding-style/article.md
4. Install/enable the plugin for your editor that integrates with ESLint. The majority of editors have one.

Here's an example of an `.eslintrc` file:
Here's an example of an `eslint.config.js` file:

@AKzar1el AKzar1el Nov 2, 2026

Copy link
Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The example uses ESM import/export in eslint.config.js. That file will not parse as an ES module in an existing project with "type": "commonjs" in package.json. Could the tutorial use eslint.config.mjs for the ESM example, or explain that eslint.config.js needs an ESM project (and that CommonJS projects can use require/module.exports)? ESLint documents this distinction in Configuration Files.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer
@AKzar1el AKzar1el AKzar1el left review comments
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

review needed Review needed, please approve or request changes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@1t1sCooL @AKzar1el @javascript-translate-bot
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.