1.0.1 • Published 9 months ago

@joshreep/captain-hooks v1.0.1

Weekly downloads
-
License
MIT
Repository
github
Last release
9 months ago

CodeQL CI codecov

:pirate_flag: Captain Hooks :pirate_flag:

Captain Hooks is a collection of clever react hooks to help make everyday react development a bit more delightful. These hooks are ones that I have used in my own personal projects and thought I'd make them available to anyone else interested.

Installation

If you're using npm:

npm i @joshreep/captain-hooks

If you're using yarn

yarn add @joshreep/captain-hooks

The hooks:

  • useAsync - A hook for rendering dynamic UIs based on the status of an async request.
  • useEventListener - A hook for adding event listeners and automatically cleaning them up.
  • useHistory - A hook for adding undo/redo functionality.
  • useIdleTimer - A hook for adding idle functionality.
  • useIsMounted - A hook for determining if the component is mounted or not.
  • useLocalStorage - A stateful hook that persists through page refresh.
  • useMemoCompare - A hook to memoize a value using a compare function.
  • useMountedState - An alternative to React.useState that only sets state if component is mounted.
  • usePrevious - A hook for comparing the current state of a value and the previous state
  • useScript - A hook for dynamically adding a script to a page.
  • useToggle - A hook for toggling a boolean state

Contributing:

This project uses yarn instead of npm. It also uses typescript for static type checking.

Installing deps

After you clone the repo, run yarn install to install all dev and peer dependencies. Captain Hooks is a zero dependency module and we'd like to keep it that way! 😎

Committing changes

When commiting any changes, please follow the conventional commit guidlines as it allows us to automate our changelog and versioning. Commitlint is also installed on this repo, so if you try to commit without adhearing to conventional commits, it will block the commit and flash a warning message.

Testing

Before commiting any changes, it's encouraged to lint your code and run tests. This will happen anyway in the CI workflow, but it is nicer to fail quickly and privately. Run yarn lint to lint, yarn test to run the test suites. If you are introducing any new functionality or changing any existing funtionality, please provide appropriate test coverage.

1.0.1

9 months ago

0.1.4

2 years ago

0.1.3

2 years ago

0.1.2

2 years ago

0.1.1

2 years ago

0.1.0

2 years ago