You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are enough dependents on pretty-format and its code goes to enough effort so an ES5 build is possible, that we will probably be sorry to publish the next version without it.
@skovhus In case there is more to consider beyond the browser property in package.json would you be willing to look at this?
@cpojer I guess this implies pretty-format never had a smoke test for the build-es5 subdirectory. Is it worth the effort to test it with the subset of ES5 values?
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Do you want to request a feature or report a bug?
Report an unintended regression.
What is the current behavior?
pretty-format
lacksbuild-es5
subdirectory after the excellent improvement in #3532See https://github.com/facebook/jest/pull/3532/files#diff-9b3b0a5fd27925d64d045cf1394e5143L11
What is the expected behavior?
There are enough dependents on
pretty-format
and its code goes to enough effort so an ES5 build is possible, that we will probably be sorry to publish the next version without it.@skovhus In case there is more to consider beyond the
browser
property inpackage.json
would you be willing to look at this?@cpojer I guess this implies
pretty-format
never had a smoke test for thebuild-es5
subdirectory. Is it worth the effort to test it with the subset of ES5 values?The text was updated successfully, but these errors were encountered: