v7.1.0

7.1.0 (2026-04-23)

Features

• add semantic-release with conventional commits (aeb5596)

Bug Fixes

• deps: update babel monorepo (#340) (045fa77)
• deps: update babel monorepo to ^7.28.6 (#379) (790fe75)
• deps: update babel monorepo to v7.28.3 (#307) (52c7351)
• deps: update babel monorepo to v7.28.4 (#314) (009a877)
• deps: update dependency @babel/runtime to ^7.29.2 (#401) (3d5361f)
• deps: update dependency @babel/runtime to v7.28.2 (#301) (172dff7)
• deps: update react monorepo (01a4c64)
• deps: update react monorepo (#342) (e723fec)
• simplify README release section and fix RELEASE.md numbering (0027288)

v7.0.0

Remove support for flow.

v5.2.0

Bump Version

v5.1.0

Adds missing exports

v5.0.0

Adds useSafeImperativeHandle and useSafeImperativeHandleExtraDeps

v4.0.0

Uses React 18.

v3.0.1

Fix useSafeCallback, useSafeCallbackExtraDeps, and unsafeMkCallbackFn to accept functions of any arity.

v3.0.0

Updates the type of CallbackFn related functions to avoid being able to use the any type. This effectively was allowing any to be sent as extraDeps to any of the useSafe* style hooks.

Unfortunately, with this change the TS compiler is unable to get rid of the unknown type without some help. This release requires type signatures in order to nudge the compiler in the right direction

This originally had correct inference of foo inside of the first parameter of useSafeEffectExtraDeps.
After the update the compiler will infer foo: unknown and you will be unable to use it in any meaningful way. If you supply useSafeEffectExtraDeps with the types it will work though.

const foo: Foo = ...
- useSafeEffectExtraDeps(
+ useSafeEffectExtraDeps<{foo: Foo}>(
  ({ foo }) => {
    //Do stuff with foo
  },
  { foo: { value: foo, comparator: (a, b) => a === b } }
);

v2.0.1

Improves hook interfaces by removing ambiguous {} type.

v2.0.0

Migrated to TypeScript