Skip to content

fix: packaging hygiene — peers, types/exports map, files whitelist - #135

Open
kuraydev wants to merge 1 commit into
masterfrom
fix/packaging-hygiene
Open

fix: packaging hygiene — peers, types/exports map, files whitelist#135
kuraydev wants to merge 1 commit into
masterfrom
fix/packaging-hygiene

Conversation

@kuraydev

@kuraydev kuraydev commented Aug 15, 2026

Copy link
Copy Markdown
Owner

Found while doing the packaging-hygiene sweep across the fleet: react/react-native were missing from peerDependencies, there was no "types" field or exports map, and the tarball ships raw TS sources, dotfiles, tsconfig.json, .github/ and a tsbuildinfo alongside the build output. Added react/react-native peers, explicit types + exports map (types condition first, matching the published build/dist layout), and a "files" whitelist keeping build/dist including local-assets (the PNGs the component require()s at runtime). The react-native-spinkit and @freakycoder/react-native-bounceable peers are BOTH genuinely imported in SearchBar.tsx and stay. No source changes. Publish as 2.0.3 after the npm account migration.

react/react-native were missing from peerDependencies, there was no
types field or exports map, and the tarball shipped TS sources,
dotfiles, tsconfig, .github and a tsbuildinfo alongside the build
output. Added react/react-native peers (spinkit and bounceable peers
kept — both genuinely imported), explicit types + exports, and a
files whitelist keeping build/dist with its local-assets. No source
changes.
@kuraydev
kuraydev force-pushed the fix/packaging-hygiene branch from 9540afa to 6c7cc86 Compare August 16, 2026 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant