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
Jest Preset Default: Update preset file extension for inclusion in NPM deployments. #19306
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
epiqueras added [Type] Bug
An existing feature does not function as intended
[Package] Jest preset
/packages/jest-preset-default
labels
Dec 23, 2019
epiqueras requested review from ajitbohra, gziolo, nerrad and ntwb as code owners
December 23, 2019 15:02
This was published in |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Package] Jest preset
/packages/jest-preset-default
[Type] Bug
An existing feature does not function as intended
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.
We switched to using a
.js
file preset without updating the relevant deploy whitelist entry inpackage.json
.