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 v8.37.0 release highlights #428

Merged
merged 1 commit into from
Mar 28, 2023
Merged

docs: Publish v8.37.0 release highlights #428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 7 additions & 2 deletions src/content/blog/2023-03-28-eslint-v8.37.0-released.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,16 +3,21 @@ layout: post
title: ESLint v8.37.0 released
teaser: "We just pushed ESLint v8.37.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
- mdjermanovic
categories:
- Release Notes
tags:
- Release
---


## Highlights

* Rules can now use [`SourceCode#getScope(node)`](/docs/latest/extend/custom-rules#accessing-variable-scopes) to get the [scope](/docs/latest/extend/scope-manager-interface#scope-interface) of the given node. The `node` argument is mandatory. This method works the same as `context.getScope()` but isn't limited to the currently traversed node. The `context.getScope()` method is now considered deprecated in favor of `SourceCode#getScope(node)`. This change is part of the [implementation of language plugins](https://github.com/eslint/eslint/issues/16999).
* Parsers and plugins can now export a [`meta` object](/docs/latest/extend/plugins#metadata-in-plugins) with `name` and `version` properties to allow for easier debugging and more effective caching. In the [new config system](/docs/latest/use/configure/configuration-files-new), ESLint uses these values when serializing configuration objects (for example, the [--print-config](/docs/latest/use/command-line-interface#--print-config) CLI option) and when determining whether cached lint results (the [`--cache`](/docs/latest/use/command-line-interface#--cache) CLI option) are still valid. If a parser/plugin provides `meta`, ESLint can now invalidate caches when a new version of the parser/plugin is installed.
* In the new config system, [`languageOptions.parser`](/docs/latest/use/configure/configuration-files-new#configuring-a-custom-parser-and-its-options) must now be a parser object. Referencing parsers by `"pluginName/parserName"` is no longer supported.
* The [require-unicode-regexp](/docs/rules/require-unicode-regexp) rule now provides [suggestions](/docs/latest/extend/custom-rules#providing-suggestions) for some of the problems it reports.



Expand Down