-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes issue with preversion script exposing the new updated package information instead of the currently existing one #51
Conversation
…nformation instead of the currently existing one
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.
Looks good to me. Thank you!
I believe this will be a semver-major change, so I'm gonna keep this PR open until npm@7
is ready to go out, and it should go in with that. Cheers!
@zkat Cool, thanks! In the meantime, I'm adding manual support in our |
@zkat Don't forget about this one ;) |
@zkat Friendly reminder about this PR |
@luislobo it's labeled as |
@isaacs Any news on getting this merged? We have had to workaround this issue reading the file ourselves to get the real information |
It's 2020 March already. Any particular reason why this isn't already merged? |
Because it's a semver-major change, and npm 7 hasn't gone out yet? |
I ask stupid questions. :) But man this should've been a patch. |
@isaacs is this going to be included in npm 7? |
So, this patch won't be in v7, because that section of code has been rewritten, and But here's what the
Let me know if there's more to do here, or if this meets your need. Thanks! |
Looks good to me! |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Fixes issue with preversion script exposing the new updated package information instead of the currently existing one
Addresses issue described in https://npm.community/t/npm-version-preversion-npm-package-version/1406