fix(cli): avoid building __typetests__
files
#27089
Merged
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.
Why
During load-time benchmarking of individual files, I noticed we are building
__typetests__
into thebuild
directory of the cli. This would then be included in the release itself.See https://cdn.jsdelivr.net/npm/@expo/cli@0.17.5/build/src/start/server/type-generation/__typetests__/
How
**/__typetests__/**
when building with SWCTest Plan
Minor change, and testable through
npm pack
. Make surebuild
does not include the__typetests__
folder.Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).