Version Details and Security Vulnerabilities

Version 1.3.99 of @swc/core, a high-performance JavaScript and TypeScript compiler, introduces subtle but potentially impactful changes compared to its predecessor, version 1.3.96. Both versions maintain the core functionality of providing a faster alternative to Babel, evident in their shared dependencies like @swc/types and @swc/counter. However, examining the devDependencies reveals distinct updates.

Notably, @napi-rs/cli has been bumped from version 2.14.1 to 2.16.5 indicating potential improvements in the native Rust bindings, which power much of SWC's speed. This could translate to better performance or enhanced compatibility with different environments. Although the versions of most dev dependencies like testing and linting related packages are consistent, the difference in @napi-rs/cli could mean better integration with the Rust-based tooling ecosystem.

The most apparent change lies within the optionalDependencies. While both versions offer pre-built binaries for various platforms (darwin-x64, darwin-arm64, linux-x64-gnu, etc.), version 1.3.96 includes @swc/core-linux-arm-gnueabihf, which is absent in 1.3.99. This suggests a potential removal of support for that particular architecture in the newer release. However, the package maintainers added @swc/core-win32-arm64-msvc to the optional dependencies of the new version, pointing towards a better support for windows based arm architectures. Developers targeting embedded Linux systems using arm-gnueabihf should therefore pay close attention. The releaseDate also indicates the new version is more recent, therefore it is probably more secure to move to the latest version if you are not dependent on arm-gnueabihf architecture.