Version Details and Security Vulnerabilities

📦

@oxc-project/types

0.78.0

Comparision Betweeen 0.78.0 and 0.77.3

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

40.06 KB

Version 0.78.0 Details

@oxc-project/types version 0.78.0 is now available, succeeding version 0.77.3 and providing developers with the latest type definitions for the Oxc AST (Abstract Syntax Tree) nodes. Both versions maintain essential characteristics, including the MIT license, ensuring broad freedom of use, and their origin within the oxc project, hosted on GitHub within the npm/oxc-types directory. The packages are authored by Boshen and the oxc contributors with funding gratefully accepted through GitHub sponsors.

A key detail for developers to note is the releaseDate. Version 0.78.0 was published on July 24, 2025 substantially after version 0.77.3, which came out on July 20, 2025. This newer release date signifies that version 0.78.0 incorporates the most recent updates and refinements to the type definitions. While the file count remains consistent at 4, and the unpacked size is identical at 41020 bytes, implying similar overall content volume, the updated release typically suggests improvements, bug fixes, or enhancements to the type definitions themselves.

Developers should prioritize using version 0.78.0 to leverage the latest advancements and ensure compatibility with the evolving Oxc ecosystem. While the immediately visible changes might be subtle, staying current with the latest version guarantees access to the stable and improved type definitions, crucial for seamless integration and accurate representation of the Oxc AST within their projects. It is always advisable for developers to check the project's changelog or release notes on GitHub for a detailed breakdown of the specific changes incorporated in version 0.78.0.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.