Version Details and Security Vulnerabilities

📦

@oxc-project/types

0.76.0

Comparision Betweeen 0.76.0 and 0.75.1

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.76.0 Details

@oxc-project/types, a crucial dependency for developers working with the Oxc toolchain and Abstract Syntax Trees (ASTs), has released version 0.76.0, succeeding the previous stable version 0.75.1. Both versions provide essential type definitions for Oxc AST nodes, ensuring type safety and improved developer experience when manipulating and analyzing JavaScript code within the Oxc ecosystem. While the core functionality remains consistent – offering well-defined types for representing code structures – subtle improvements and potential bug fixes likely differentiate the two.

From a developer's perspective, the upgrade from 0.75.1 to 0.76.0 promises enhanced stability and potentially refined type definitions. While the unpacked size (41020 bytes) and file count (4) are identical, indicating a similar overall structure, the newer version benefits from a more recent release date (July 8, 2025), suggesting a concentrated effort towards addressing issues and incorporating recent developments within the Oxc project.

Developers can leverage these typings to build custom linters, code analysis tools, or transformations that operate on the Oxc-generated AST. The MIT license grants broad usage rights, and contributions are encouraged. The unchanged unpacked size suggests efficiency and a focus on the essential types needed, minimizing bloat. Always consult the official Oxc project documentation for the comprehensive changelog and migration guides for the most accurate details about specific changes. The repository link on GitHub serves as the primary resource for reporting issues, contributing, and staying updated.

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.