React.useRef
with an immediate setter and read-only value.
Aids useCallback
and useMemo
for better memoization, reduce wasted render, and properly signal render loop.
By using useRefFrom
, React component developers can make sure their custom hooks are properly memoized.
Following examples shows how useRefFrom
help decoupling mutation for callbacks.
Return function from useCallback
could change on every render.
const MyComponent = ({ message }: { message: string }) => {
// `handleClick` changes on every update to `message`.
const handleClick = useCallback(() => {
alert(message);
}, [message]);
return <button onClick={handleClick}>Click me</button>;
};
Decoupling message
from useCallback
by useRef
.
const MyComponent = ({ message }: { message: string }) => {
const messageRef = useRef<string>();
messageRef.current = message;
// `handleClick` stay intact regardless of `message`.
const handleClick = useCallback(() => {
// `messageRef.current` is `string | null`, unsafe casting is required.
alert(messageRef.current as string);
}, [messageRef]);
return <button onClick={handleClick}>Click me</button>;
};
Decoupling message
from useCallback
by useRefFrom
. It also helps typing and immutability.
const MyComponent = ({ message }: { message: string }) => {
const messageRef = useRefFrom<string>(message);
// `handleClick` stay intact regardless of `message`.
const handleClick = useCallback(() => {
// `messageRef.current` is `readonly string`.
alert(messageRef.current);
// ❌ `messageRef.current` is read-only. The following line will fail at compile-time.
messageRef.current = 'Hello, World!'.
}, [messageRef]);
return <button onClick={handleClick}>Click me</button>;
};
function useRefFrom<T>(value: T): RefObject<T> & { get current(): T };
The RefObject<T>
returned by useRefFrom()
will be read-only and cannot be set. This is by design.
If you see TypeScript compilation error related to useRefFrom.d.ts
, please make sure you are using TypeScript 4.3 or up.
node_modules/use-ref-from/lib/types/useRefFrom.d.ts:3:5 - error TS1131: Property or signature expected.
3 get current(): T;
~~~
Like us? Star us.
Want to make it better? File us an issue.
Don't like something you see? Submit a pull request.