Gathering detailed insights and metrics for file-saver-es
Gathering detailed insights and metrics for file-saver-es
Gathering detailed insights and metrics for file-saver-es
Gathering detailed insights and metrics for file-saver-es
npm install file-saver-es
Typescript
Module System
Node Version
NPM Version
99.7
Supply Chain
99.5
Quality
75.2
Maintenance
100
Vulnerability
100
License
JavaScript (100%)
Total Downloads
5,614,822
Last Day
2,256
Last Week
30,150
Last Month
193,529
Last Year
2,274,314
21,721 Stars
332 Commits
4,378 Forks
367 Watching
10 Branches
57 Contributors
Latest Version
2.0.5
Package Id
file-saver-es@2.0.5
Size
10.33 kB
NPM Version
6.14.8
Node Version
14.15.1
Publised On
21 Nov 2020
Cumulative downloads
Total Downloads
Last day
-76.4%
2,256
Compared to previous day
Last week
-38.4%
30,150
Compared to previous week
Last month
-1.3%
193,529
Compared to previous month
Last year
26.2%
2,274,314
Compared to previous year
If you need to save really large files bigger than the blob's size limitation or don't have enough RAM, then have a look at the more advanced StreamSaver.js that can save data directly to the hard drive asynchronously with the power of the new streams API. That will have support for progress, cancelation and knowing when it's done writing
FileSaver.js is the solution to saving files on the client-side, and is perfect for web apps that generates files on the client, However if the file is coming from the server we recommend you to first try to use Content-Disposition attachment response header as it has more cross-browser compatiblity.
Looking for canvas.toBlob()
for saving canvases? Check out
canvas-toBlob.js for a cross-browser implementation.
Browser | Constructs as | Filenames | Max Blob Size | Dependencies |
---|---|---|---|---|
Firefox 20+ | Blob | Yes | 800 MiB | None |
Firefox < 20 | data: URI | No | n/a | Blob.js |
Chrome | Blob | Yes | 2GB | None |
Chrome for Android | Blob | Yes | RAM/5 | None |
Edge | Blob | Yes | ? | None |
IE 10+ | Blob | Yes | 600 MiB | None |
Opera 15+ | Blob | Yes | 500 MiB | None |
Opera < 15 | data: URI | No | n/a | Blob.js |
Safari 6.1+* | Blob | No | ? | None |
Safari < 6 | data: URI | No | n/a | Blob.js |
Safari 10.1+ | Blob | Yes | n/a | None |
Feature detection is possible:
1try { 2 var isFileSaverSupported = !!new Blob; 3} catch (e) {}
It is possible to save text files in IE < 10 without Flash-based polyfills.
See ChenWenBrian and koffsyrup's saveTextAs()
for more details.
Blobs may be opened instead of saved sometimes—you may have to direct your Safari users to manually
press ⌘+S to save the file after it is opened. Using the application/octet-stream
MIME type to force downloads can cause issues in Safari.
saveAs must be run within a user interaction event such as onTouchDown or onClick; setTimeout will prevent saveAs from triggering. Due to restrictions in iOS saveAs opens in a new window instead of downloading, if you want this fixed please tell Apple how this WebKit bug is affecting you.
saveAs()
from file-saver1import { saveAs } from 'file-saver';
1FileSaver saveAs(Blob/File/Url, optional DOMString filename, optional Object { autoBom })
Pass { autoBom: true }
if you want FileSaver.js to automatically provide Unicode text encoding hints (see: byte order mark). Note that this is only done if your blob type has charset=utf-8
set.
require()
1var FileSaver = require('file-saver'); 2var blob = new Blob(["Hello, world!"], {type: "text/plain;charset=utf-8"}); 3FileSaver.saveAs(blob, "hello world.txt");
1var blob = new Blob(["Hello, world!"], {type: "text/plain;charset=utf-8"});
2FileSaver.saveAs(blob, "hello world.txt");
1FileSaver.saveAs("https://httpbin.org/image", "image.jpg");
Using URLs within the same origin will just use a[download]
.
Otherwise, it will first check if it supports cors header with a synchronous head request.
If it does, it will download the data and save using blob URLs.
If not, it will try to download it using a[download]
.
The standard W3C File API Blob
interface is not available in all browsers.
Blob.js is a cross-browser Blob
implementation that solves this.
1var canvas = document.getElementById("my-canvas");
2canvas.toBlob(function(blob) {
3 saveAs(blob, "pretty image.png");
4});
Note: The standard HTML5 canvas.toBlob()
method is not available in all browsers.
canvas-toBlob.js is a cross-browser canvas.toBlob()
that polyfills this.
You can save a File constructor without specifying a filename. If the file itself already contains a name, there is a hand full of ways to get a file instance (from storage, file input, new constructor, clipboard event). If you still want to change the name, then you can change it in the 2nd argument.
1// Note: Ie and Edge don't support the new File constructor,
2// so it's better to construct blobs and use saveAs(blob, filename)
3var file = new File(["Hello, world!"], "hello world.txt", {type: "text/plain;charset=utf-8"});
4FileSaver.saveAs(file);
1# Basic Node.JS installation 2npm install file-saver --save 3bower install file-saver
Additionally, TypeScript definitions can be installed via:
1# Additional typescript definitions 2npm install @types/file-saver --save-dev
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 9/14 approved changesets -- score normalized to 6
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
25 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-12-23
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