[bare][ci] Remove native-component-list from bare-expo if running on the CI #7170
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
Since I added
native-component-list
tobare-expo
app (#6868), tests are sometimes failing due to timeouts. It mostly refers only to the first test suite because it's the first to trigger code bundling. Excludingnative-component-list
code frombare-expo
when it's run on the CI should solve the problem or at least reduce code bundling time.How
If
process.env.CI
orprocess.env.NO_NCL
is truthy, then we will use custom resolver for all imports fromnative-component-list
- the custom resolver will simply returnnull
- so its main navigators won't be included in the bottom tabs navigator.Test Plan
yarn run test:web
inapps/bare-expo
works locally and I seenative-component-list
paths in webpack's logs and the total time forBasic
tests is high.CI=true yarn run test:web
also passes and takes significantly less time.yarn run ios
works as expected.CI=true yarn run ios
works as well, with justtest-suite
app included.sdk/web_test_suite
passes and bundling time is much better now.