chore: Remove unused App component breaking test watch mode #143
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 PR is a:
[ ] New feature
[ ] Enhancement/Optimization
[ ] Refactor
[x] Bugfix
[ ] Test for existing code
[ ] Documentation
Summary
Updated Jest dep to
^23.4.0
, fixing fix: properly reprint resolver errors in watch mode jestjs/jest#6407 which caused ourtest:dev
script to appear to hang when files were modified and Jest cache was absent. The original behavior froze at this message:The new version of Jest properly prints the error message:
Removed the
App
component, which is now unused due to theMagentoResolver
callingRootComponents
directly, and was the source of the mapping error above. Future errors of this kind will appear early and should be easier to diagnose and fix.Additional information