Use node instead of webpack config for jest #12974
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weltenwort
added
Team:Core
|
The test failure is about a license not being permissible. Seems to be unrelated, since this did not change any dependencies. jenkins, test this |
|
@weltenwort I think you just need to rebase master. A fix for the ua-parser license was just merged recently. |
cjcenizal
approved these changes
Jul 19, 2017
This allows for testing components that use generators or async/await as well as for the usage of these features in the tests files.
weltenwort
force-pushed
the
fix/babel-jest-node-config
branch
from
a1051c6 to
0d7d5d5
Compare
kimjoar
approved these changes
Jul 19, 2017
weltenwort
added a commit
to weltenwort/kibana
that referenced
this pull request
Jul 21, 2017
weltenwort
added a commit
that referenced
this pull request
Jul 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows for testing components that use generators or async/await as
well as for the usage of these features in the tests files.
There is a separate issue with the jest cache being invalidated when some of our configuration files changed, but that will be tackled in a different PR.