Need help with beautiful-react-hooks?
Click the โ€œchatโ€ button below for chat support from the developer who created it, or find similar developers for support.

About the developer

4.3K Stars 241 Forks MIT License 377 Commits 13 Opened issues


๐Ÿ”ฅ A collection of beautiful and (hopefully) useful React hooks to speed-up your components and hooks development ๐Ÿ”ฅ

Services available


Need anything else?

Contributors list

CI/CD Coverage StatusLicense: MIT npm GitHub stars

Beautiful React Hooks

A collection of beautiful (and hopefully useful) React hooks to speed-up your components and hooks development

Usage example

๐Ÿ‡ฌ๐Ÿ‡ง English | ๐Ÿ‡จ๐Ÿ‡ณ ็ฎ€ไฝ“ไธญๆ–‡ | ๐Ÿ‡ฎ๐Ÿ‡น Italiano | ๐Ÿ‡ช๐Ÿ‡ธ Espaรฑol | ๐Ÿ‡บ๐Ÿ‡ฆ Ukrainian | ๐Ÿ‡ง๐Ÿ‡ท Brazilian Portuguese | ๐Ÿ‡ต๐Ÿ‡ฑ Polski | ๐Ÿ‡ฏ๐Ÿ‡ต ๆ—ฅๆœฌ่ชž

๐Ÿ’ก Why?

React custom hooks allow to abstract components' business logic into single reusable functions.
So far, we've found that most of the hooks we've created and therefore shared between our internal projects have quite often a similar gist that involves callback references, events and components' lifecycle.
For this reason we've tried to sum up that gist into

: a collection of (hopefully) useful React hooks to possibly help other companies and professionals to speed up their development process.

Furthermore, we created a concise yet concrete API having in mind the code readability, focusing to keep the learning curve as lower as possible so that the it can be used and shared in bigger teams.

-- Please before using any hook, read its documentation! --

โ˜•๏ธ Features

  • Concise API
  • Small and lightweight
  • Easy to learn
  • Functional approach
  • Fully written in JS (although TS types are supported)

๐Ÿ•บ Install

by using

$ npm install beautiful-react-hooks

by using

$ yarn add beautiful-react-hooks

๐ŸŽจ Hooks


Contributions are very welcome and wanted.

To submit your custom hook, please make sure your read our CONTRIBUTING guidelines.

Before submitting a new merge request, please make sure:

  1. You have updated the package.json version and reported your changes into the CHANGELOG file
  2. make sure you run
    npm test
    npm build
    before submitting your merge request.
  3. make sure you've added the documentation of your custom hook (you can possibly use the HOOKDOCUMENTATIONTEMPLATE to document your custom hook).
  4. make sure you've updated the
    file with your hook types.

Made with


This library is provided and sponsored by:

As part of our commitment to support and contribute to the open source community.

Icon made by Freepik from

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.