Skip to content

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

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

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

Conversation

@kuraydev

@kuraydev kuraydev commented Aug 15, 2026

Copy link
Copy Markdown
Owner

Packaging-hygiene pass mirroring react-native-bouncy-checkbox #822. package.json only, no source changes.

  • peerDependencies: already present (react >= 16.x.x, react-native >=0.63.x) — kept as-is.
  • types + exports map: added, pointing at the published build/dist output (ToggleButton.js / .d.ts), types condition first, ./package.json export included.
  • files whitelist: the published 0.1.0 tarball ships .husky/ hooks, TypeScript sources (lib/), tsconfig.json, tsconfig.tsbuildinfo, .eslintrc.js, .prettierrc, .commitlintrc.json — now trimmed to build/dist.
  • Version: 0.1.0 → 0.1.1.
  • No runtime dependencies declared and none needed — nothing to remove.

⚠️ No LICENSE file in the repo (package.json says MIT) — worth adding separately.

Publish as 0.1.1 after the npm account migration.

The package had no types field or exports map, and the published
tarball shipped .husky hooks, TypeScript sources, tsconfig and lint
dotfiles. types + exports now point at the published build/dist
output with the types condition first, and a files whitelist trims
the tarball to build/dist. Existing react/react-native peer
dependencies were already present and are kept as-is. Version bumped
to 0.1.1; no source changes.
@kuraydev
kuraydev force-pushed the fix/packaging-hygiene branch from 652601c to 63c8371 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