[Bug] A hook to only copy to clipboard

[erayerdin]

Description

useClipboard or useCopyToClipboard hooks return [string, (text: string) => Promise<void>] where 0 is the content from the clipboard while 1 is the function to write into it. The problem is, Chrome asks for permission which might look suspicious for some users, not good in terms of UX and it is reasonable to only write into clipboard.

Reproduction

Steps to reproduce the behavior:

1. Install @reactuses/core
2. Use hook useClipboard or useCopyToClipboard
3. Chrome asks for permission.

Expected Behavior

Chrome should not ask for permission. There must be a hook to only write into the clipboard.

Environment

• OS: Linux
• Browser: 148.0.7778.178 (Official Build, ungoogled-chromium) (64-bit)
• React version: 19.2.6
• @reactuses/core version: 6.3.2

Additional Context

None.

[childrentime]

Thanks for the report — this is a valid concern.

You're right that navigator.clipboard.readText() triggers Chrome's permission prompt, while writeText() does not. The current useClipboard is too aggressive: it reads on mount, on copy/cut events, and on window focus, which is unnecessary for the common "click to copy" use case.

The plan is to add a { read?: boolean } option to useClipboard (defaulting to true for backward compatibility). Setting read: false will skip all clipboard-read logic and the permission prompt entirely.

Would you like to submit a PR for this? If not, no worries — I'll implement it as soon as possible.

[erayerdin]

I will submit a PR. Before that, what should we name this new hook? I'd suggest useCopyToClipboard but that seems to be an alias for useClipboard. If we use that, that'd be a breaking change for library users. What do you suggest?

a. Go for useCopyToClipboard, which would be a breaking change for library users?
b. Go for another name, which I cannot really come up with anything. I'm open to your suggestions.

[childrentime]

Great, thanks for picking this up!

I'd actually prefer to avoid adding a new hook here. My suggestion is to extend the existing useClipboard with an options argument instead:

useClipboard()                 // current behavior, reads enabled (backward compatible)
useClipboard({ read: false })  // write-only, no permission prompt

Benefits:

• No breaking change — useClipboard and the useCopyToClipboard alias keep working exactly as today.
• No naming bikeshed.
• Users opt out of the read path (and all its listeners) with a single flag.

Implementation sketch:

• interface.ts: change the signature to (options?: { read?: boolean }) => readonly [string, (txt: string) => Promise<void>].
• index.ts: when read === false, skip the useEffect initial read and don't attach the copy / cut / focus listeners. text simply stays as ''.
• Default read to true so existing callers are unaffected.

If you'd rather have a dedicated write-only hook, useCopy would be my pick — short, unambiguous, and doesn't collide with the existing alias. But I think the options approach is cleaner. WDYT?

[erayerdin]

Let's keep it options. Another hook with useCopy is too ambiguous. I will implement it and submit a PR.