Updated path-complete-extname #1
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I just recently released path-complete-extname@1.0.0 in order to mitigate a vulnerability report that traces back to the original node@0.10 implementation in which the module was based on.
The solution was to rewrite the module basing it in the current node implementation and publish a new major version. I'm reaching out to all libraries described on npm dependencies list to make sure they can all get the new patched version as soon as possible.
I decided for a major release in order to be able to properly follow semver from now on and to properly reflect the stable state of the library that has been around for 4 years 😊
Let me know if there are any concerns and please feel free to review all the code changes.
Best,
Ruy Adorno