Evolve react-simplikit as a general-purpose utility library and consolidate the mobile package back into the main one.
As-is
- The main package lives in
packages/core, which doesn't match its published name react-simplikit.
- Mobile web hooks/utils are published separately as
@react-simplikit/mobile (packages/mobile).
- Consumers need two installs and two import roots for one library.
To-be
packages/core → packages/react-simplikit, so the directory matches the published package.
- Move the hooks/utils from
packages/mobile into packages/react-simplikit.
- Expose them via a subpath import (e.g.
react-simplikit/mobile); the exact import shape (root re-export vs subpath-only) is decided in the PR.
Why
One general-purpose package is the direction we committed to; the core/mobile split (#329) optimized for a mobile-focused roadmap we're no longer pursuing.
Must verify
Evolve react-simplikit as a general-purpose utility library and consolidate the mobile package back into the main one.
As-is
packages/core, which doesn't match its published namereact-simplikit.@react-simplikit/mobile(packages/mobile).To-be
packages/core→packages/react-simplikit, so the directory matches the published package.packages/mobileintopackages/react-simplikit.react-simplikit/mobile); the exact import shape (root re-export vs subpath-only) is decided in the PR.Why
One general-purpose package is the direction we committed to; the core/mobile split (#329) optimized for a mobile-focused roadmap we're no longer pursuing.
Must verify
@react-simplikit/mobilenpm package.