minified-size
v3.1.0
Published
Estimates the size of minified and gzipped/brotlied JavaScript, CSS and HTML files.
Downloads
68
Maintainers
Readme
minified-size
Estimates the size of minified and gzipped/brotlied JavaScript, CSS and HTML files very fast. Check, how much space will a particular source take in the minified output.
Note: If you use Node.js 8 or 9, install a version 1.x
. Versions 2.x
require Node.js 10 or newer. (They need support for asynchronous generators.)
Command-line Usage
Make sure that you have Node.js >= 10 installed. Install the minified-size
package globally by your favourite package manager:
npm i -g minified-size
pnpm i -g minified-size
yarn global add minified-size
Print the original, expected minified, gzipped and brotlied sizes of a sample file:
$ minified-size lib/index.js
lib/index.js: 10.8 kB, 5.09 kB, 2.12 kB, 1.86 kB
Running minified-size
without any parameters will print usage instructions:
Usage: minified-size [options] <file>, ... | --
Options:
-V, --version output the version number
-l, --language [name] specifies the input language (default: "js")
-j, --json print results in the JSON format
-r, --raw-sizes print sizes in bytes as integers
-o, --no-original-size prevents printing the size of the original code
-m, --no-minified-size prevents printing the size of the minified code
-g, --no-gzipped-size prevents printing the size of the gzipped code
-b, --no-brotlied-size prevents printing the size of the brotlied code
-s, --source-type [type] sets JavaScript source type (module or script)
-t, --no-total prevents printing the total sizes
-i, --minifier [minifier] chooses the JavaScript minifier (default: "swc")
-h, --help display help for command
All four sizes are estimated by default. File paths may contain wildcards.
If "--" is entered instead of files, the standard input will be read.
Stylesheets are recognized by the extension ".css", or they can be forced
by the language "css" on the command line. Web pages are recognized by the
extension ".htm[l]", or they can be forced by the language "html".
The JavaScript minifier can be "swc", "esbuild", "terser" or "babel".
Errors
If parsing of the input or its minification fails, a colourful error message with additional information will be printed instead of the computed sizes. For example, a typo "exort" instead of "export":
$ minified-size test/invalid.js
test/invalid.js(1,7): unknown: Unexpected token, expected ";"
> 1 | exort default {
| ^
2 | "compressed": "
3 | "
4 | }` } ]
Programmatic Usage
Make sure that you use Node.js >= 16. Install the minified-size
package locally by your favourite package manager:
npm i minified-size
pnpm i minified-size
yarn add minified-size
Get the original, expected minified, gzipped and brotlied sizes (in bytes) of a sample file:
const { getMinifiedSizes } = require('minified-size')
const results = await getMinifiedSizes({ files: [ 'lib/index.js' ] })
// [ { file: 'lib/index.js',
// originalSize: 10788,
// minifiedSize: 5087,
// gzippedSize: 2122,
// brotliedSize: 1861 } ]
If you process a lot of files, you can use an asynchronous generator, which yields results one-by-one to get them earlier, instead of returning an array with all of them together:
const { generateMinifiedSizes } = require('minified-size')
const resultGenerator = generateMinifiedSizes({
files: [ 'public/**/*.(js|css|html)' ]
})
for (;;) {
const result = await resultGenerator.next()
if (result.done) {
break
}
const {
error, file, originalSize, minifiedSize, gzippedSize, brotliedSize
} = result.value
if (error) {
console.info(`${file}: ${originalSize}, ${minifiedSize}, ${gzippedSize}, ${brotliedSize}`)
} else {
console.error(`${file}: ${error}`)
}
}
You can compute total sizes from all file results:
const { getMinifiedSizes, computeTotalSizes } = require('minified-size')
const results = await getMinifiedSizes({ files: [ 'foo.js', 'bar.js' ] })
const total = computeTotalSizes(results)
// { total: true,
// originalSize: 89745,
// minifiedSize: 8562,
// gzippedSize: 2341,
// brotliedSize: 2065 }
Options
language
- a string specifying the input language ("js", "css" or "html")files
- an array of strings with file paths to load and processstreams
- an array of readable streams with source code to processsources
- an array of strings with source code to processgzip
- a boolean to disable estimating the gzipped output size, or an object with options for gzip.brotli
- a boolean to disable estimating the brotlied output size, or an object with parameters for brotli.minifier
- a string choosing the JavaScript minifier ("swc" - default, "esbuild", "terser" or "babel")
Errors
If parsing of the input or its minification fails, the returned object will contain an error
key instead of the computed sizes:
const minifiedSize = require('minified-size')
const files = [ 'test/invalid.js' ]
const results = await minifiedSize({ files })
// [ { file: 'test/invalid.js',
// error: {
// reason: 'unknown: Unexpected token, expected ";"',
// line: 1,
// column: 7,
// message: `test/invalid.js(1,7): unknown: Unexpected token, expected ";"
//
// > 1 | exort default {
// | ^
// 2 | "compressed": "
// 3 | "
// 4 | }` } ]
Unicode
Let us say, that you minify scripts using UTF-8 literals a lot:
message = "䅬朤堾..."
If you run such input through babel-minify, you may become a lot bigger output instead of a smaller one, because it escapes non-latin characters:
message="\u416C\u6724\u583E\u605B\u0825\u6120\u4C20..."
Look for an option, that will make your minifier retain the Unicode literals unchanged, or converts all escaped Unicode code points to literals. You could also post-process the minified output yourself by the following method:
function replaceEscapedUnicodeCharacters (source) {
return source.replace(/\\u([\w]{4})/gi, (match, code) =>
String.fromCharCode(parseInt(code, 16)))
}
The size computation done by minified-size
uses the function above to ensure correct results until the issue babel-minify/619 is resolved.
Other minifiers (swc, esbuild and terser) do not suffer from this issue. (esbuild needs the option charset=utf8
added.)
Performance
The JavaScript minifier affects the performance the most. The most efficient one is swc, but because it cannot minify both modules and scripts using the same options, esbuild is used by default. Other minifiers (esbuild, swc, terser and babel-minify) can be chosen as a workaround by the minifier
option, if the default minifier cannot process some source, or just to compare the results of the minifiers.
An example of measuring a cocktail of 6.6 MB in 69 JavaScript libraries (Require, Underscore, jQuery, Backbone, Backbone.Radio, Handlebars, Marionette, Moment, Moment-Timezone, Ally, Hammer, Less etc.) shows the huge difference between the minifiers:
$ time minified-size -ogbr -i swc libs/*.js
...
total: 2924862
2.12s user 0.40s system 134% cpu 1.868 total
$ time minified-size -ogbr -i esbuild libs/*.js
...
total: 2961126
1.02s user 0.25s system 125% cpu 1.012 total
$ time minified-size -ogbr -i terser libs/*.js
...
total: 2953313
15.07s user 0.42s system 167% cpu 9.273 total
$ time minified-size -ogbr -i babel libs/*.js
...
total: 2966286
32.77s user 1.14s system 143% cpu 23.651 total
Contributing
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
License
Copyright (c) 2018-2023 Ferdinand Prantl
Licensed under the MIT license.