Moves babel-jest into jest-config rather than jest-runtime #5931
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I noticed that jest-runtime doesn't make any require to babel-jest, so it doesn't need to be there. Inversely, jest-config needs babel-jest to be able to work properly (because of normalize), so it needs to be declared as a dependency.
I guess it was put this way so that babel-core would be used for both jest-config and jest-runtime, but that's an optimization that should be left to the package manager.
Test plan
Existing tests should pass, no new test should be needed.