fix: packaging hygiene — peers, types/exports map, files whitelist - #1099
Open
kuraydev wants to merge 1 commit into
Open
fix: packaging hygiene — peers, types/exports map, files whitelist#1099kuraydev wants to merge 1 commit into
kuraydev wants to merge 1 commit into
Conversation
The published tarball shipped both v5-example/ and v6-example/ apps (gradle wrappers, Podfile.locks, yarn.lock, debug keystore), .husky, .idea and dotfiles. react/react-native were missing from peers. Added a files whitelist (build/dist only), react/react-native peers next to the existing @react-navigation/native peer, and an explicit types + exports map. Version set to 2.3.2 since npm already has 2.3.1 while the repo said 2.3.0. No source changes.
kuraydev
force-pushed
the
fix/packaging-hygiene
branch
from
August 16, 2026 18:38
afb4f99 to
fd4967d
Compare
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.
Found while doing the packaging-hygiene sweep across the fleet: the published tarball ships BOTH v5-example/ and v6-example/ apps (gradle wrappers, Podfile.locks, yarn.lock, even a debug keystore), plus .husky, .idea and dotfiles. react/react-native were missing from peers. Added a "files" whitelist (build/dist only), react/react-native peers alongside the existing @react-navigation/native peer (genuinely imported, kept), and an explicit types + exports map matching the published build/dist layout. Also note: npm already has 2.3.1 while the repo said 2.3.0, so version goes straight to 2.3.2. No source changes. Publish as 2.3.2 after the npm account migration.