-
Notifications
You must be signed in to change notification settings - Fork 783
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
CLI: Implement --require option #1271
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.
Awesome! This is great, and unlocks some really nice patterns...
@@ -0,0 +1,6 @@ | |||
const resolve = require( "resolve" ); |
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.
Not related to this PR, but we seem to have grown a fair number of files in bin/
that are not intended as standalone CLI entry points. We should consider moving these to src/
instead.
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.
👍 agreed, though I would like to ensure we keep some clear separation between CLI code and library code (just means we likely need src/cli
or something)
This is so cool! This should mean |
This PR implements a
--require
option for the CLI. It allows for any number of dependencies or files to berequire
d prior to the test suite run actually starting.Fixes #1222