fix: make yarn test pass across workspaces - #579
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR Description
Fix two failures in root
yarn test: the Expo template test could not loadtest-rendererafter #578, and the React Navigation workspace exited with an error because it has no tests.Add
test-renderer ~1.1.0to the template to match React 19.1, update the lockfile, and include a template patch changeset. Allow an empty test suite only in the React Navigation workspace with--passWithNoTests.How to test?
yarn install --immutable— passes with existing peer dependency warnings.yarn test— all three workspace tasks pass (one Expo test passes, the core library has one TODO, and React Navigation has no tests).git diff --check— pass.