-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update vulnerable packages and replace deprecated mocha.opts #41
Update vulnerable packages and replace deprecated mocha.opts #41
Conversation
"mocha": { | ||
"ui": "tdd" |
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.
I think this has to be added as a command line argument, here:
Line 21 in 545d2fe
-- node_modules/.bin/mocha |
Otherwise I don't think it's going to be applied in dependent projects.
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.
Thx for the hint.
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.
Ah, I forgot about mocha.opts
, sorry for the misdirection. See #41 (comment)
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.
I think I've come full circle. Your original code was correct (prior to bf9fb04). We just need to tell other users of the lib to use the same approach. Currently the README advertises using mocha.opts
. What do you think @davidchambers ?
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.
I agree, Aldwin. I suggest the following:
Configurable via variables (
min-branch-coverage
) and themocha
field of package.json.
@wuweiss sorry for the conflicting feedback. It seems we need two things to be completed for this PR to be acceptable:
Commit, force push, and we should be good to go. Right, @davidchambers ? |
That sounds good to me, Aldwin. :) If you would like, @wuweiss, Aldwin or I could make these two small changes. I know what it's like to receive feedback on a pull request once my attention is elsewhere. |
Sorry I was AFC, will do the changes this evening. Thanks for your help. |
bf9fb04
to
8b08107
Compare
0adc87d
to
49c8641
Compare
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.
Thank you for this contribution, @wuweiss. :)
No description provided.