- No runtime npm dependencies in @kamod-hooks/core
- ESM + TypeScript build
- Per-hook subpath imports, e.g. @kamod-hooks/core/useToggle
- Browser-native APIs where possible: ResizeObserver, IntersectionObserver, Fullscreen API, URLSearchParams, History API
- Hooks for async requests, debounce/throttle, localStorage/sessionStorage, URL state, virtual lists, WebSocket, drag/drop, responsive breakpoints, theme handling, and more
I started this because I often use Preact for small, fast frontend projects, but many useful hook libraries are still React-first. Kamod Hooks is meant to fill that gap without pulling in React-specific assumptions like react-router.
It is still early, so I would especially appreciate feedback on:
- API compatibility with ahooks
- Which hooks are most important for real-world Preact projects
I originally built it for my own setup (multiple devices, encrypted files, etc.), and it kind of grew from there.
Not everyone has a NAS at home, so the idea behind syncding.com was to provide a simple, encrypted online Syncthing hub that just works without the usual setup — with built-in ZFS snapshots for versioning and recovery.
Always cool to see others using similar workflows.
I built Kamod Hooks, a Preact hooks library inspired by and ported from ahooks.
The goal is to bring a broad set of practical React-style hooks to the Preact ecosystem, while keeping the package lightweight and Preact-native.
Repo: https://github.com/kamod-ch/kamod-hooks
Some details:
- Preact-only peer dependency
- No runtime npm dependencies in @kamod-hooks/core
- ESM + TypeScript build
- Per-hook subpath imports, e.g. @kamod-hooks/core/useToggle
- Browser-native APIs where possible: ResizeObserver, IntersectionObserver, Fullscreen API, URLSearchParams, History API
- Hooks for async requests, debounce/throttle, localStorage/sessionStorage, URL state, virtual lists, WebSocket, drag/drop, responsive breakpoints, theme handling, and more
I started this because I often use Preact for small, fast frontend projects, but many useful hook libraries are still React-first. Kamod Hooks is meant to fill that gap without pulling in React-specific assumptions like react-router.
It is still early, so I would especially appreciate feedback on:
- API compatibility with ahooks
- Which hooks are most important for real-world Preact projects
- Bundle/tree-shaking behavior
- Missing docs or examples
- Whether the package structure feels right
Thanks!