Gathering detailed insights and metrics for cb-rollup-plugin-filesize
Gathering detailed insights and metrics for cb-rollup-plugin-filesize
Gathering detailed insights and metrics for cb-rollup-plugin-filesize
Gathering detailed insights and metrics for cb-rollup-plugin-filesize
npm install cb-rollup-plugin-filesize
Typescript
Module System
Min. Node Version
Node Version
NPM Version
52
Supply Chain
88.6
Quality
67.8
Maintenance
50
Vulnerability
94.8
License
JavaScript (100%)
Total Downloads
1,031
Last Day
1
Last Week
3
Last Month
15
Last Year
146
117 Commits
1 Watching
4 Branches
1 Contributors
Minified
Minified + Gzipped
Latest Version
9.0.0-5
Package Id
cb-rollup-plugin-filesize@9.0.0-5
Unpacked Size
34.39 kB
Size
9.59 kB
File Count
9
NPM Version
6.14.5
Node Version
12.16.1
Cumulative downloads
Total Downloads
Last day
0%
1
Compared to previous day
Last week
-40%
3
Compared to previous week
Last month
275%
15
Compared to previous month
Last year
-24.7%
146
Compared to previous year
A rollup plugin to show filesize in the cli
npm install rollup-plugin-filesize
1import { rollup } from 'rollup'; 2import filesize from 'rollup-plugin-filesize'; 3 4rollup({ 5 entry: 'main.js', 6 plugins: [ 7 filesize() 8 ] 9}).then(...)
type: boolean
default: true
Whether to show minified size or not
type: boolean
default: true
Whether to show Gzipped size or not
type: boolean
default: false
Whether to show Brotli size or not
Note: this feature is experimental and may be changed in a future release.
type: "release", ``"build"
, or "none"
default: "none"
Indicates how, if any, comparisons will be shown between the
output.file
file size as it was and as it is now being written.
If set to "release"
, will compare the file size at present to that of
the last npm release.
If set to "build"
, the size of the file that is now being built will
be compared to the immediately previous build. This means that if you run
Rollup multiple times with this option, the info on the previous package
size will be lost (since Rollup will have overwritten your copy), so with
this option, you will need to consult your terminal history to see what the
file size was prior to your changes. This option may be useful if you wish
to compare size changes incrementally as you are developing rather than
comparing to your last release.
type : object
default : {}
See the options here
(Note that this replaces the deprecated optional render
function option.)
type : A reporter string (currently "boxen" only), a function, or an array thereof.
Defaults to "boxen".
After rendering occurs, you may wish to pass on the collected file data, e.g., to build a badge for filesizes (as does filesize-badger).
You can use reporter
to do so:
1filesize({ 2 reporter: [ 3 function (options, bundle, { 4 minSize, gzipSize, brotliSize, bundleSize, 5 fileName, 6 // "showBeforeSizes: release" 7 lastVersion, 8 // "showBeforeSizes: "release" or "showBeforeSizes": "build" 9 bundleSizeBefore, brotliSizeBefore, minSizeBefore, gzipSizeBefore 10 }) { 11 // If a promise is returned, it will be awaited before rendering. 12 return promise; 13 }, 14 ], 15});
type: string
default : 'dark'
options : 'dark'/'light'
choose based on your terminal theme.
MIT
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
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
dependency not pinned by hash detected -- score normalized to 0
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
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
42 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-01-27
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