Gathering detailed insights and metrics for clipboard
Gathering detailed insights and metrics for clipboard
Gathering detailed insights and metrics for clipboard
Gathering detailed insights and metrics for clipboard
✂️ Modern copy to clipboard. No Flash. Just 3kb gzipped 📋
npm install clipboard
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
34,041 Stars
396 Commits
3,980 Forks
418 Watching
9 Branches
60 Contributors
Updated on 28 Nov 2024
JavaScript (99.14%)
TypeScript (0.54%)
Shell (0.31%)
Cumulative downloads
Total Downloads
Last day
-6.9%
303,039
Compared to previous day
Last week
2.6%
1,740,731
Compared to previous week
Last month
12.2%
7,311,016
Compared to previous month
Last year
-11.7%
80,187,403
Compared to previous year
3
25
Modern copy to clipboard. No Flash. Just 3kb gzipped.
Copying text to the clipboard shouldn't be hard. It shouldn't require dozens of steps to configure or hundreds of KBs to load. But most of all, it shouldn't depend on Flash or any bloated framework.
That's why clipboard.js exists.
You can get it on npm.
npm install clipboard --save
Or if you're not into package management, just download a ZIP file.
First, include the script located on the dist
folder or load it from a third-party CDN provider.
1<script src="dist/clipboard.min.js"></script>
Now, you need to instantiate it by passing a DOM selector, HTML element, or list of HTML elements.
1new ClipboardJS('.btn');
Internally, we need to fetch all elements that matches with your selector and attach event listeners for each one. But guess what? If you have hundreds of matches, this operation can consume a lot of memory.
For this reason we use event delegation which replaces multiple event listeners with just a single listener. After all, #perfmatters.
We're living a declarative renaissance, that's why we decided to take advantage of HTML5 data attributes for better usability.
A pretty common use case is to copy content from another element. You can do that by adding a data-clipboard-target
attribute in your trigger element.
The value you include on this attribute needs to match another's element selector.
1<!-- Target --> 2<input id="foo" value="https://github.com/zenorocha/clipboard.js.git" /> 3 4<!-- Trigger --> 5<button class="btn" data-clipboard-target="#foo"> 6 <img src="assets/clippy.svg" alt="Copy to clipboard" /> 7</button>
Additionally, you can define a data-clipboard-action
attribute to specify if you want to either copy
or cut
content.
If you omit this attribute, copy
will be used by default.
1<!-- Target --> 2<textarea id="bar">Mussum ipsum cacilds...</textarea> 3 4<!-- Trigger --> 5<button class="btn" data-clipboard-action="cut" data-clipboard-target="#bar"> 6 Cut to clipboard 7</button>
As you may expect, the cut
action only works on <input>
or <textarea>
elements.
Truth is, you don't even need another element to copy its content from. You can just include a data-clipboard-text
attribute in your trigger element.
1<!-- Trigger --> 2<button 3 class="btn" 4 data-clipboard-text="Just because you can doesn't mean you should — clipboard.js" 5> 6 Copy to clipboard 7</button>
There are cases where you'd like to show some user feedback or capture what has been selected after a copy/cut operation.
That's why we fire custom events such as success
and error
for you to listen and implement your custom logic.
1var clipboard = new ClipboardJS('.btn'); 2 3clipboard.on('success', function (e) { 4 console.info('Action:', e.action); 5 console.info('Text:', e.text); 6 console.info('Trigger:', e.trigger); 7 8 e.clearSelection(); 9}); 10 11clipboard.on('error', function (e) { 12 console.error('Action:', e.action); 13 console.error('Trigger:', e.trigger); 14});
For a live demonstration, go to this site and open your console.
Each application has different design needs, that's why clipboard.js does not include any CSS or built-in tooltip solution.
The tooltips you see on the demo site were built using GitHub's Primer. You may want to check that out if you're looking for a similar look and feel.
If you don't want to modify your HTML, there's a pretty handy imperative API for you to use. All you need to do is declare a function, do your thing, and return a value.
For instance, if you want to dynamically set a target
, you'll need to return a Node.
1new ClipboardJS('.btn', { 2 target: function (trigger) { 3 return trigger.nextElementSibling; 4 }, 5});
If you want to dynamically set a text
, you'll return a String.
1new ClipboardJS('.btn', {
2 text: function (trigger) {
3 return trigger.getAttribute('aria-label');
4 },
5});
For use in Bootstrap Modals or with any other library that changes the focus you'll want to set the focused element as the container
value.
1new ClipboardJS('.btn', {
2 container: document.getElementById('modal'),
3});
Also, if you are working with single page apps, you may want to manage the lifecycle of the DOM more precisely. Here's how you clean up the events and objects that we create.
1var clipboard = new ClipboardJS('.btn'); 2clipboard.destroy();
This library relies on both Selection and execCommand APIs. The first one is supported by all browsers while the second one is supported in the following browsers.
42+ ✔ | 12+ ✔ | 41+ ✔ | 9+ ✔ | 29+ ✔ | 10+ ✔ |
The good news is that clipboard.js gracefully degrades if you need to support older browsers. All you have to do is show a tooltip saying Copied!
when success
event is called and Press Ctrl+C to copy
when error
event is called because the text is already selected.
You can also check if clipboard.js is supported or not by running ClipboardJS.isSupported()
, that way you can hide copy/cut buttons from the UI.
A browser extension that adds a "copy to clipboard" button to every code block on GitHub, MDN, Gist, StackOverflow, StackExchange, npm, and even Medium.
Install for Chrome and Firefox.
MIT License © Zeno Rocha
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 5/8 approved changesets -- score normalized to 6
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
27 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More