minor versioning correction, dependency chain issues in child project, vulnerable vue version #29
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.
Hi there ^^
Sorry for intruding.
I'm currently working on a set of applications aimed at writers of varying skill levels, and while looking around for a suitable WYSIWYG interface, I found UmoEditor, which fits my aesthetic vision and satisfies my gadget armamentarium needs.
Dependency chain has a vulnerable vue version in one place.
Luckily it was your plugin and that issue was not complex problem, just forgotten version update, nothing special really.
Hope that you approve it soon, because your gadget is great and it's a shame to leave it unused because of those stupid 2 lines that npm audit is screaming for :)
best regards
Sett