Version Details and Security Vulnerabilities

📦

rollup-plugin-ts

1.3.7

Comparision Betweeen 1.3.7 and 1.3.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

2.57 MB

2.54 MB

Version 1.3.7 Details

Rollup Plugin TS version 1.3.7 introduces a set of updates and refinements compared to its predecessor, version 1.3.0. Primarily a build tool enhancement, this plugin empowers developers to seamlessly integrate TypeScript code into Rollup-based workflows. One key difference lies in the dependencies. Version 1.3.7 updates several dependencies to newer versions, including @babel/core, browserslist, @babel/runtime, @babel/preset-env, @rollup/pluginutils. A notable addition in the dependencies is @wessberg/stringutil. These upgrades often bring performance improvements, bug fixes, and new features to the underlying tools. A similar uplift happened in the devDependencies where multiple packages like eslint, rollup, typescript, @typescript-eslint/parser and others where updated to more recent versions. Another critical aspect is the Typescript version. While version 1.3.0 was using version 4.0.0-beta, version 1.3.7 moved to a more stable typescript":"^4.1.0-dev.20201026. The peer dependencies remain largely the same, ensuring compatibility with existing Rollup and TypeScript projects. Developers should consider upgrading to 1.3.7 to benefit from the latest improvements and ensure compatibility with modern TypeScript and Babel features. The updated dependencies could also potentially address security vulnerabilities present in older versions. Inspecting the changelog is highly recommended for a comprehensive understanding of all changes.

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.