Fix Critical Build Error: Exclude Test Files from Metro Bundle#315
Draft
Fix Critical Build Error: Exclude Test Files from Metro Bundle#315
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Co-authored-by: rodneyg <6868495+rodneyg@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Critical Build Error: Exclude Test Files from Metro Bundle
Fix Critical Build Error: Exclude Test Files from Metro Bundle
Jun 11, 2025
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
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.
Problem
The production build was failing because test files (
*.test.ts) were being included in the final JavaScript bundle, causing a fatalReferenceError: Cannot access 'G' before initializationon the live server when the application attempted to render the/onboarding/userTyperoute.Root Cause
The
metro.config.jsfile was not configured to ignore test files. Metro bundler was incorrectly treatingapp/onboarding/userType.test.tsas application source code, leading to compilation errors and runtime crashes when Jest mocks and test code were included in the production bundle.Solution
Modified
metro.config.jsto explicitly exclude test files from the bundling process using Metro'sresolver.blockListconfiguration:Changes Made
resolver.blockListto Metro configuration*.test.(js|ts|tsx)files from bundling*.spec.(js|ts|tsx)files from bundling for completenessVerification
npx expo start) starts successfully without Metro errorsnpx expo export) completes without the previous CSS parsing errorThis is a minimal, surgical fix that addresses the deployment-blocking issue while maintaining all existing functionality.
Fixes #314.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
cdp.expo.devnode /home/REDACTED/work/SafeDose/SafeDose/node_modules/.bin/expo export(dns block)node /home/REDACTED/work/SafeDose/SafeDose/node_modules/.bin/expo start --web(dns block)node /home/REDACTED/work/SafeDose/SafeDose/node_modules/.bin/expo export --platform web(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.