This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 62
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
2 additions
and
2 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
208a033
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is this version different from the previous one?
208a033
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears to be the same. Just the version number in package.json is increased by one.
This version was probably published by mistake, such as by accidentally running
npm publish
twice instead of once.you can confirm by fetching the tarballs from the npm package registry (using
npm pack
), extracting the tarballs, and then doing a recursive diff, like this shell script will do for you:From that, you ultimately get this output:
Furthermore, the difference from 5.7.1 is really only a slightly newer minimum nan package dependency, which should make no difference to users of this package, since the dependency range as specified was already inclusive of all possible newer nan 2.x releases above 2.14.0....