bump stylus-supremacy to 5.0.0 & overrides vulnerabilities#3
Open
adrienWeiss wants to merge 1 commit intoqnp:masterfrom
Open
bump stylus-supremacy to 5.0.0 & overrides vulnerabilities#3adrienWeiss wants to merge 1 commit intoqnp:masterfrom
adrienWeiss wants to merge 1 commit intoqnp:masterfrom
Conversation
This file contains hidden or 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
1 participant
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.
Hello,
stylus-supremacy was recently updated to 5.0.0
I was digging around its dependencies to see if I could get rid of some package overrides but unfortunately it still relies on
stylintwhich is not maintained anymore and parent of vulnerable dependencies.Still, after playing a bit I figured why not take the opportunity to still update stylus-supremacy on your project and also patch its own declared vulnerabilities.
We still need to have 2
overrides(or resolutions for yarn) though.I also bumped
vitestwhich was also coming with vulnerabilities.I know we really shouldn't mind that much about package vulnerabilities but as you may know some of us are dealing with company policies which take no real interest in making sure those represent real danger 😓
Please let me know if you'd rather bump these dependencies a different way.
Again, thanks for this project, really precious for people like me which are still dealing with large codebases in Vue/stylus 🙏