chartist VS terser

The author went through the effort of creating a marketing site with documentation and examples.

https://gionkunz.github.io/chartist-js/

(Full disclosure: this is a real-world design decision from Chartist, an open-source data visualization library I maintain and contribute to.)

During my intial search i came across some outdated libraries like javascript-obfuscator and uglify-js(as if javascript code can get any uglier, am I right?). Then, I stumbled upon Terser, a modern library that supports ES6.

Example: You've got a main.js file that's as long as a Tolstoy novel. Fix: Use tools like UglifyJS or Terser to minify your code. They'll squeeze out all the unnecessary bits and give you a sleeker, faster-loading file.

They can do it, it is just turned off by default and require more advanced configuration.

https://github.com/terser/terser#cli-mangling-property-names...

Minifying is a common practice for optimizing production code. (for example, using Terser to minify and mangle JavaScript).

Minification: UglifyJS, Terser

Terser is JavaScript compressor that can minified specific method names.

Every release build of React Native uses terser to reduce the size of your JavaScript. And it operation can be omitted for Staging/Beta builds.

A minifier makes your code more compact so that it loads faster. Popular minifiers: Terser, swc.

There are many minifiers such as terser and uglify. But, because minifying also require to parse the JS, it is actually possible to use esbuild and SWC to minify the code. Here's a benchmark of the main minifiers.

This next one will help us reduce final bundle size by minifying the generated code. It's called rollup-plugin-terser and uses terser under the hood to minify the code.