Back to Explore

jsx-eslint/jsx-ast-utils

GitHub
1 watchersOpen source

Last release: 6/25/2019

jsx-ast-utils is an AST utility module for statically analyzing JSX syntax. It helps evaluate AST objects for JSX elements, which is useful for writing linting rules, and provides helper functions like hasProp, hasAnyProp, hasEveryProp, getProp, and functions to read prop names and values. It also includes lists of common JSX event handler props (for example, grouped by event type).

Project status

  • The source appears to be maintained in the sense that the upstream repo has an activity signal (last push on 2026-02-25), but the most recent historical “update” entries provided are from 2019, so tagged update cadence looks low or irregular based on this evidence.
  • Apparent update/recent release cadence (from the provided update summaries): updates were shipped in 2017, then 2019-04, then 2019-06, and there are no newer update notes shown after 2019.

AI summary generated Today

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v2.2.0

    6/25/2019

    Release 2.2.0 updates JSX AST value extraction to handle TypeScript-specific AST node types and changes behavior when encountering unknown AST nodes. The release also upgrades dependencies and adjusts CI, plus updates tests to reflect the new non-throwing behavior.

    Breaking
  • v2.1.0

    4/19/2019

    v2.1.0 extends the JSX prop AST value extraction to handle newer syntax, including optional chaining and additional TypeScript node types (TSAsExpression, TSNonNullExpression). It also improves evaluation for template literals containing undefined, and adds support for object spread constructs in prop values. The release appears focused on broader AST coverage rather than introducing a new public API.

    Features
  • v2.0.0

    7/7/2017

    v2.0.0 introduces an API contract change around `propName`, and includes multiple JSX value extraction improvements. The provided release notes are effectively empty (only a reference to #50), so most behavioral and API changes are not explicitly documented there.

    BreakingFeatures