Provides an Esprima-compatible JavaScript AST type system and traversal utilities based on the Mozilla JS Parser API, including node builders and type checks. Useful for building, validating, and walking JavaScript abstract syntax trees.
Project status
- Maintenance status: The repository is not showing frequent, public updates in the provided release history (latest shown version is v0.16.1 from 2022-12-13). An upstream GitHub push occurred on 2024-06-12, but no corresponding recent release updates or notes are included here, so overall it appears quiet rather than actively shipping regular updates.
- Update cadence: Based on the provided version chronology, updates have not been consistent, with multi-month to multi-year gaps (for example, 2021-12 to 2022-12). Because only one upstream push is given for 2024 and no additional recent release info is provided, the current cadence is unclear, but the visible release stream is slow.
AI summary generated
Recent updates
v0.16.1
v0.16.1 updates the AST type definitions and builder interfaces to support additional class-related fields. It also changes the CI Node.js matrix and bumps several dev dependencies in package.json and package-lock.json.
Featuresv0.16.0
v0.16.0 contains a major internal refactor (moving code from lib/ to src/, updating build and publishing layout) plus expanded AST type coverage for newer JavaScript/TypeScript syntax. The diff also introduces a new shared helper for preserving CommonJS default export behavior (maybeSetModuleExports) and adds a package.json exports map. Release notes were not provided, so the changes below are inferred directly from the code diff.
Featuresv0.15.2
Release v0.15.2 was published on 2021-12-02, but the publisher did not include any release notes. As a result, the specific changes in this version, including potential bug fixes, security updates, or breaking changes, are not documented in the provided information.
v0.15.1
v0.15.1 updates the AST builder and TypeScript type definitions to better model modern ECMAScript proposals, including import attributes and static blocks. It also changes the way ImportAttribute and StaticBlock are typed and built, and adds a new optional assertions field to certain import/export declaration nodes.
Featuresv0.15.0
Release v0.15.0 has no published release notes. The code diff shows a substantial refactor of how operator and proposal-related AST node types are composed, alongside additions of new syntax node definitions (records, tuples, module expressions, decimal literals, static blocks) and updated scope/path typing and behavior.
BreakingFeaturesv0.14.2
v0.14.2 updates the library’s AST type definitions and builders to support optional chaining using the newer ChainExpression and ChainElement model. It also adjusts scoping logic to recognize RestElement patterns, and bumps several dev dependencies (including recast and ts-node) with corresponding lockfile changes. Release notes were not provided, so these changes are not documented in the publisher notes.
BreakingFeaturesv0.14.1
Release v0.14.1 contains a small internal schema change around Flow's `ObjectTypeIndexer`, plus a few development dependency bumps. No release notes were provided, so the changes below represent what the code diff shows actually changed between v0.14.0 and v0.14.1.
v0.14.0
Release v0.14.0 reorganizes the AST type definitions into newer ES version and proposal modules (es2016 to es2020, plus es-proposals), and expands the covered JavaScript, JSX, and Flow node shapes. The release notes section is empty, so the actual behavior and type contract changes below are not documented by the publisher.
Featuresv0.13.4
v0.13.4 ships without any publisher-provided release notes. The code diff shows primarily TypeScript AST definition updates (named tuple members, type predicate shape changes), plus a runtime behavior adjustment in scope handling for catch clauses, and a substantial dev dependency/toolchain refresh.
BreakingFeaturesv0.13.3
Release v0.13.3 was published on 2020-03-27, but the publisher did not include any release notes. No documented new features, fixes, or breaking changes are available from the provided release data, so developer impact cannot be determined from the notes alone.