-
Notifications
You must be signed in to change notification settings - Fork 37
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
security vuln fix, grammar + clarification #133
Conversation
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.
Don't know how I feel about adding this to the instructions when building/running. Npm warns itself that this can break dependencies, and it's never a good idea to manually update a dependencies dependency.
You should attempt upgrading vuepress to 2.0.0-rc.2
first, instead of updating a sub-depenency. This may break things, make sure it works before pushing.
web dev moment |
so do we update the versions through the |
There's nothing different about this than any other programming language.
Avoid editing package-lock.json. edit package.json
For the future, please submit different patches in different prs, it helps with reviewing and merging |
js devs coping is funny |
gotcha, should i resubmit the other changes? (except the package-lock.json) |
😭😭😭 |
yea package-lock editing is really bad practice |
@ethanaobrien do i just open up a seperate pr? |
Yes, one for rewording/grammar, one for the security issue |
will do |
redoing last pr pretty much #133
wrong repo |
npm returned a security vulnerability, had to bump
vite
to4.5.2
(hence the changes topackage-lock.json
) plus i fixed some grammar toindex.md
,template.md
(template for supported devices), andfaq.md
. mentioned the security vuln fix(es) with the line i added incontributing.md
screenshot: