Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Publish v9.12.0 release highlights #647

Merged
merged 2 commits into from
Oct 4, 2024
Merged

docs: Publish v9.12.0 release highlights #647

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b881c0
docs: Publish v9.12.0 release highlights
fasttime Oct 4, 2024
b3ee9a4
Update src/content/blog/2024-10-04-eslint-v9.12.0-released.md
fasttime Oct 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 16 additions & 2 deletions src/content/blog/2024-10-04-eslint-v9.12.0-released.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,18 +3,32 @@ layout: post
title: ESLint v9.12.0 released
teaser: "We just pushed ESLint v9.12.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release."
image: release-notes-minor.png
draft: true
authors:
- eslintbot
- fasttime
categories:
- Release Notes
tags:
- Release
---

## Highlights

### Experimental configuration file resolution

One of the big changes in ESLint v9.0.0 was the new config system which switched from looking for config files relative to the file being linted to starting the search from the current working directory. While this dramatically decreased the complexity of config file lookup, it also had an unintended side effect: monorepos could no longer include a separate `eslint.config.js` file in each project directory and then run ESLint with one command from the root. To address this, we're working on a new configuration file resolution algorithm that more closely mirrors how the eslintrc config system worked.

This new algorithm also starts the search from the file being linted, restoring the monorepo use case and also making it possible to run ESLint from anywhere on any file and get the same results each time. Because this feature is experimental, you’ll need to use the `unstable_config_lookup_from_file` feature flag, like this:

```shell
npx eslint --flag unstable_config_lookup_from_file
```

For more information on this feature, see [Experimental Configuration File Resolution](/docs/latest/use/configure/configuration-files#experimental-configuration-file-resolution). For more information on using feature flags, see [Feature Flags](/docs/latest/flags/).

### Other notable changes

* [`RuleTester`](/docs/latest/integrate/nodejs-api#ruletester) now supports custom `before` and `after` hooks for test cases.
* The `complexity` rule has a new option [`variant`](/docs/latest/rules/complexity#variant) to support modified cyclomatic complexity.



Expand Down