-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat: add MOCHA_OPTIONS env variable #4835
Conversation
@juergba have you had a chance to look this over? |
This PR hasn't had any recent activity, and I'm labeling it |
This PR hasn't had any recent activity, and I'm labeling it |
@outsideris I still need this feature. Would I be able to get some feedback? |
Yes! |
Yay! We're not quite ready to start reviewing PRs yet, but hope to soon. Note that I don't see any linked issues. The contributing guidelines right now ask for that so that folks can discuss the change first. We'll continue to require that after #5038. Was there any impetus for this PR besides what's in the description? |
There's no separate issue, the PR description contains all the context I have. I can create an issue if you'd like though. |
That would be lovely, yes please! Note that the three of us new maintainers are still ramping up on the project, so it might be some weeks (or even months 😞) before we have enough context to really triage the issue and review this PR. We'll do our best to get to it soon though! |
That's alright. It's been two years, what's another month or two? |
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.
Sweet! Really pleasing to see such a clean implementation. And with thorough tests! 👏
Just requesting changes on docs.
ce9ba6b
to
d79e034
Compare
Description of the Change
The
MOCHA_OPTIONS
environment variable is a space-separated list of command-line options. It essentially copies node's approach with NODE_OPTIONSThe config priority is:
MOCHA_OPTIONS
environment variable..mocharc.c?js
,.mocharc.ya?ml
,mocharc.json
)mocha
prop ofpackage.json
lib/mocharc.json
)Alternate Designs
Yargs has support for env variables: https://yargs.js.org/docs/#api-reference-envprefix
However, using this feature would result in a separate env variable for each option:
Ex:
MOCHA_BAIL
MOCHA_ALLOW_UNCAUGHT
MOCHA_FAIL_ZERO
I decided to to go with
MOCHA_OPTIONS
because it seems less intrusive and that's how node does it too.Why should this be in core?
I don't see how it could live anywhere else.
Benefits
My specific use-case is specifying
MOCHA_OPTIONS='--inspect-brk'
when callingnpm run test
from vim.Possible Drawbacks
Applicable issues
Fixes #4330.