childrentime/reactuse
by Various
115+ production-ready React Hooks for sensors, UI, state & browser APIs. Tree-shakable, SSR-safe, TypeScript-first. Used by Shopee, PDD & Ctrip. Inspired by VueUse.
MCP
childrentime/reactuse
Added 7 June 2026
Overview
A collection of 115+ production-ready React Hooks covering sensors, UI, state, and browser APIs. It is tree-shakable, SSR-safe, and TypeScript-first, inspired by VueUse and used by companies like Shopee, PDD, and Ctrip.
Best for
Best for
React developers building complex web apps who want ready-made hooks for common browser and UI tasks
Use cases
- Add reusable hooks for browser APIs like geolocation or clipboard
- Manage UI state such as media queries or element visibility
- Implement sensor-based interactions like mouse position or device orientation
Notes
A collection of 115+ production-ready React Hooks covering sensors, UI, state, and browser APIs. It is tree-shakable, SSR-safe, and TypeScript-first, inspired by VueUse and used by companies like Shopee, PDD, and Ctrip.
1,011 stars on GitHub. Last updated 2026-05-27. Licensed Unlicense.
Use cases
- Add reusable hooks for browser APIs like geolocation or clipboard
- Manage UI state such as media queries or element visibility
- Implement sensor-based interactions like mouse position or device orientation
Pros
- Large library of hooks reduces boilerplate for common patterns
- Tree-shakable and SSR-safe for efficient production builds
- TypeScript-first with strong typing out of the box
Cons
- Dependency on external library may increase bundle if not tree-shaken properly
- Not all hooks may be maintained at the same pace as core React
- Learning curve for developers unfamiliar with hook-based patterns
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Large library of hooks reduces boilerplate for common patterns
- Tree-shakable and SSR-safe for efficient production builds
- TypeScript-first with strong typing out of the box
Cons
- Dependency on external library may increase bundle if not tree-shaken properly
- Not all hooks may be maintained at the same pace as core React
- Learning curve for developers unfamiliar with hook-based patterns