Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
react-use-handler
Advanced tools
In most cases useCallback
hook should work for you. But if it doesn't, you're in the right place :)
This is an analogue of bound methods in class components, but for hooks. Here is an example of a class component:
class ClassComponent extends React.Component {
myHandler = (data) => {
doSmth(data, this.props.prop1)
}
render() {
return <ChildComponent onEvent={this.myHandler} />
}
}
or in a more brutal way
class ClassComponent extends React.Component {
constructor() {
this.myHandler = this.myHandler.bind(this)
}
myHandler(data) {
doSmth(data, this.props.prop1)
}
render() {
return <ChildComponent onEvent={this.myHandler} />
}
}
myHandler
method has access to actual props
and state
while ChildComponent
receives the same instance of myHandler
in its prop on every render.
This feature can be usefull in some cases.
Suppose you are using ChildComponent and want to get notifications from it on some events:
<ChildComponent onCoolEvent={(data) => { /* .... */ })} />
Actually ChildComponent
receives newly created instance of a function in onCoolEvent
prop on each render.
Sometimes it is not a problem, sometimes it is. Sometimes useCallback
will help you. In case it's a problem and useCallback
is not enough just wrap that function with useHandler
like this
<ChildComponent onCoolEvent={useHandler((data) => { /* .... */ })} />
useHandler
guarantees that its return value will never change, but it'll always call the actual instance of your function with correct bindings.
Suppose you are developing a component with some expensive async effects. Like so:
const EffectiveComponent = ({ prop1, prop2, onFirstStage, onSecondStage }) => {
/*...*/
useEffect(() => {
let mounted = true
void async function () {
// very expensive calculations1....
if (!mounted) return
onFirstStage()
// even more expensive calculations2....
if (!mounted) return
onSecondStage()
}()
return () => { mounted = false }
}, [prop1, prop2])
}
Let's imagine you appreciate your effect very much and do not want to restart it if some of event props change. You want your effect to just do its work and emit some events. But there is a problem. If on...
prop change you should restart your effect otherwise eventually it will call obsolete things. If you restart your effect on minor prop changes you can end up with some bad user experience.
To escape this you could make a ref, store there your event handler and then call it inside your effect without any trouble. But that's exactly what useHandler
does! Let's use it:
const EffectiveComponent = ({ prop1, prop2, onFirstStage, onSecondStage }) => {
/*...*/
const onFirstEvent = useHandler(onFirstStage)
const onSecondEvent = useHandler(onSecondStage)
useEffect(() => {
let mounted = true
void async function () {
// very expensive calculations #1....
if (!mounted) return
onFirstEvent()
// even more expensive calculations #2....
if (!mounted) return
onSecondEvent()
}()
return () => { mounted = false }
}, [prop1, prop2])
return /*....*/
}
useHandler
also handles the case when callback is actually undefined or null. In those cases it calls nothing and returns undefined.
This hook makes a proxy for a function. It guarantees to return the same instance across multiple renders. It calls nothing if the actual handler is nullish.
f
Func? Some being recreated function to wrap.Returns Func function.
MIT © Vadzim Zieńka
1.2.0
FAQs
turn recreatable function to a persistent one
The npm package react-use-handler receives a total of 28 weekly downloads. As such, react-use-handler popularity was classified as not popular.
We found that react-use-handler demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.