-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
chore: convert jest-cli and jest-validate to esm #8874
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,12 @@ | |
| * LICENSE file in the root directory of this source tree. | ||
| */ | ||
|
|
||
| import * as cli from 'jest-cli'; | ||
| export { | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. followup from last question, should we ditch these exports as well? A reason not to is that we don't really have a programmatic API yet (and won't from jest 25), so all we'd do is ask people to import directly from
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As long as we don't have clear vision of the new API, I wouldn't change that just yet |
||
| SearchSource, | ||
| TestScheduler, | ||
| TestWatcher, | ||
| getVersion, | ||
| runCLI, | ||
| } from '@jest/core'; | ||
|
|
||
| export = cli; | ||
| export {run} from 'jest-cli'; | ||
Uh oh!
There was an error while loading. Please reload this page.