Fix Mock exports for external consumers #8215
Open
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.
Context / Problem
External consumers could not use the
Mockanymore because react-native-builder-bob wasn’t compiling the Mock files in their previous location. In practice that meant the published package didn’t contain a usable, compiled Mock entry for downstream projects, even though the repository had the implementation.Summary
This PR makes the Mock implementation consumable from the published package by ensuring it’s included in the build output, cleaning up a legacy entry file, and aligning package export mappings for different toolchains (including React Native).
Changes included
Move
Mockdirectory intosrcMockimplementation undersrc/MockRemove legacy
Mockentry file + adjust JestMock.tsjest.config.js(and related config) to reflect the new structureUpdate
package.jsonexport mappingsreact-nativeandsourcemappings for./Mockto ensure correct resolution for different bundlers/toolingTesting / Verification