fix(cli): bundle supported Jest CLI runtime#168
Draft
V3RON wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What is this?
Harness now ships the Jest CLI version it supports instead of relying on a consumer-installed peer. This fixes standalone CLI invocations such as yarn dlx react-native-harness init.
How does it work?
The CLI declares jest-cli 30.2 as a runtime dependency, aligned with Harness’s existing Jest 30 integration. Package managers can still deduplicate it when a compatible version is already present.
Why is this useful?
Harness commands use a known-compatible Jest runtime in both existing projects and temporary package-manager environments, avoiding missing-peer startup failures.