Version Details and Security Vulnerabilities

📦

dayjs

1.5.19

Comparision Betweeen 1.5.19 and 1.5.18

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

53.14 KB

52.44 KB

Version 1.5.19 Details

Dayjs version 1.5.19 represents a subtle yet noteworthy update to the lightweight JavaScript date library, succeeding version 1.5.18. Both versions, licensed under the MIT license, share an identical set of development dependencies, showcasing the tools used for testing, linting, and building the library such as Jest, ESLint, Rollup, and a suite of Babel-related packages for ensuring compatibility across various JavaScript environments. The core functionalities and API structure are expected to be consistent, meaning migration would be seamless for existing users.

However, developers should note specific differences. Primarily, the 'dist' section reveals that dayjs-1.5.19 occupies a slightly larger unpacked size of 54419 bytes compared to 1.5.18's 53698 bytes and contains 19 files instead of 18, pointing to potential internal code improvements, bug fixes, or new features included in the newer release. Furthermore, the release date indicates that 1.5.19 was published on May 4th, 2018, following 1.5.18 published on May 3rd, 2018, meaning the update addresses something recent to its previous release. Detailed release notes or commit history, found on the GitHub repository (https://github.com/xx45/dayjs.git), are paramount to understand the precise modifications. While both are dependency-free, minuscule package size and aiming to be a Moment.js alternative, always check for breaking changes that could impact existing implementations before upgrading, even within minor version increments.

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.