TL;DR

  • Adds Temporal API support for ES2026 globals and the no-obj-calls rule.
  • Introduces meta.languages for rules, enabling language-specific linting.
  • Includes minor bug fixes and documentation updates for improved stability.

Key Changes

  • Features: ESLint v10.2.0 introduces two notable features. It now includes official support for the Temporal API, a modern JavaScript global for advanced date and time handling, by incorporating it into the ES2026 globals. Additionally, the no-obj-calls rule has been updated to correctly recognize Temporal objects, preventing unnecessary linting warnings. A significant new capability is the meta.languages support for rules, which allows rule developers to explicitly define the programming languages a rule applies to, enhancing precision in linting environments that might involve multiple language contexts.
  • Bug Fixes: A single bug fix addresses the updating of first-party dependencies. This maintenance ensures the core linter remains stable, secure, and compatible with its internal components, contributing to overall reliability.
  • Documentation: Several documentation improvements have been implemented. Notably, the configuration objects now include language information, directly supporting the new meta.languages feature. Other updates focus on clarifying existing guidelines and updating examples.

For full details, refer to the official ESLint release notes.

Impact for QA Teams

QA teams benefit from improved code quality checks, especially for projects adopting the Temporal API. The meta.languages feature can aid in more precise static analysis for polyglot repositories or when developing custom rules for specific language subsets, reducing irrelevant warnings and focusing on critical issues.

FAQ

  • Q: What is the Temporal API? A: Temporal is a new JavaScript API for working with dates and times, designed to address shortcomings of the existing Date object.
  • Q: How does meta.languages help? A: It allows ESLint rules to declare which languages they are relevant for, potentially improving rule applicability and reducing false positives in mixed-language projects.
  • Q: Is this a critical update? A: As a minor release, it’s not critical for all users but is important for projects using or planning to use the Temporal API or those needing more granular control over rule application via meta.languages.