Version Details and Security Vulnerabilities

📦

oxc-parser

0.87.0

Comparision Betweeen 0.87.0 and 0.86.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

846.5 KB

Version 0.87.0 Details

Oxc-parser has released version 0.87.0, building upon the solid foundation of the previous stable release, version 0.86.0. Both versions serve as Node APIs for the Oxc parser, a project aimed at creating a high-performance JavaScript parser. The core functionality remains consistent, with both offering efficient parsing capabilities thanks to the underlying Rust-based implementation.

A key difference lies in the updated dependencies. Version 0.87.0 upgrades @oxc-project/types to version 0.87.0, aligning the parser with the latest type definitions within the Oxc ecosystem. Developers integrating oxc-parser should be aware of this dependency update, especially if they are directly interacting with the type system. While the developer tooling remains similar, version 0.87 makes no changes to the devDependencies, except for upgrading the napi-rs/wasm-runtime to v1.0.3, it is worth upgrading for the improvements and features or bug fixes that it includes. From a platform support perspective, the array of optional dependencies, which define native bindings for various operating systems and architectures, has been modified adding "@oxc-parser/binding-wasm32-wasi":"0.87.0".

For developers considering an upgrade, version 0.87.0 delivers the power of Javascript parsing with the underlying Rust based compiler and brings updated type definitions and targets WASM for edge deployments. If the upgrade to @oxc-project/types introduces any compatibility issues in your project, sticking with version 0.86.0 might be a more prudent choice. Regardless, oxc-parser offers a compelling option for projects demanding speed and accuracy in JavaScript parsing within a Node.js environment and offers bindings for a breadth of platforms.

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.