minification-benchmarks
bun
minification-benchmarks | bun | |
---|---|---|
15 | 288 | |
1,208 | 70,679 | |
- | 2.2% | |
9.1 | 10.0 | |
4 days ago | 2 days ago | |
TypeScript | Zig | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
minification-benchmarks
-
Extremely reducing the size of NPM package
Minifiers are used to reduce the size of the bundle. They can remove unused code, shorten expressions, and so on. And Now there are already several popular minifiers, and they continue to appear: more familiar ones - written in JavaScript - Terser and UglifyJS, even Babel has its own version of the minifier, there are also more modern SWC (written in Rust) and ESBuild (written in Go), and a bunch of other lesser-known minifiers. And I recommend you to look at this repository. It contains up-to-date test results of various popular minifiers.
-
Minify and Gzip (2022)
This minify/gzip size effect is a well known quirk to developers of javascript minifiers. The minifier's symbol mangling algorithm often has a more pronounced effect than does advanced AST optimization.
This website has real life data on the matter for popular libraries:
* https://github.com/privatenumber/minification-benchmarks
Compare the trophies indicating smallest size for Minified versus Minzipped (gzip). Generally the smallest minified size yields the smallest minified+gzip size, but there are some notable anomolies outside the range of statistical noise. It is not practical for a javascript minifier to take a compression algorithm into account - it would blow up the minify timings exponentially.
-
Bun v0.6.0 โ Bun's new JavaScript bundler and minifier
It would be helpful to see how Bun's minifier compares to the others with popular libraries:
https://github.com/privatenumber/minification-benchmarks
-
JS Uglify/Minify Gems?
JavaScript
-
Overview of the next-gen frontend dev tools
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.
-
Overworld 1.0 is Live
Here's a comparison showing the major players with comparable stats at first glance. https://github.com/privatenumber/minification-benchmarks
-
Is anyone using Google Closure Compiler? And why not?
https://esbuild.github.io/ https://github.com/privatenumber/minification-benchmarks
- Parcel v2
- I never need webpack or babel anymore
-
๐งข Stefan's Web Weekly #6
privatenumber/minification-benchmarks โ JS minification benchmarks: babel-minify, esbuild, terser, uglify-js
bun
-
Node Test Runner vs Bun Test Runner (with TypeScript and ESM)
It has a decent compatibility with both Jest and Vitest's APIs (you can track progress here so you can use it as almost a drop-in replacement for either. Just as Node's, it has describe/it, mock, test and others, but with the expect syntax (which I find more readable). For example:
-
SPA-Like Navigation Preserving Web Component State
In this third and final article in the series on HTML Streaming, we will explore the practical implementation of the Diff DOM Streaming library in web browsing. This approach will allow any website using web components to retain its state during browsing. We will discuss in detail how to achieve this step by step using VanillaJS and Bun.
-
React Server Components Example with Next.js
At Node Conference 2023, Jarred Sumner (creator of Bun) showed a demo of server components in Bun, so there is at least partial support in that ecosystem. The Bun repo provides bun-plugin-server-components as the official plugin for server components. And while I havenโt looked at it in-depth, Marz claims to be a โReact Server Components Framework for Bunโ.
- Bun โ A fast all-in-one JavaScript runtime
-
From Node to Bun: A New Dawn for JavaScript Engines?
Continuously evolving, Bun is currently optimized for MacOS and Linux, with ongoing efforts towards Windows compatibility. Tailored for resource-constrained environments like serverless functions, it emerges as an ideal solution. The Bun team is committed to achieving comprehensive Node.js compatibility and seamless integration with prevalent frameworks. For those intrigued by Bun's potential and want to give it a try, more information is available on its website at https://bun.sh/.
-
Bun - The One Tool for All Your JavaScript/Typescript Project's Needs?
Letโs say you are interested in learning more about Bun and probably give it a try. Bun has a website, where you can learn more about Bun and its features (including all the benchmark data captured in this issue), and here is the link.
-
Bun 1.1
Looks like it, it seems the 2% are mostly odd platform specific issues that the authors' did not deem very important (my assumption for the release happening anyway). AFAIK this[1] PR tries to fix them.
[1]: https://github.com/oven-sh/bun/pull/9729
-
Bun-ify Your Project
Bun has a solution for it. First of all, it already has a list of trusted dependencies. For them, Bun will execute all necessary scripts by default. Otherwise, you can add it to trustedDependecies in your package.json file. In Bun community usage of trustedDependencies is a hot topic. There are several suggestions on how to improve it.
-
I have created a small anti-depression script
Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there
-
JSR: The JavaScript Registry
I think maybe I was unclear. I'm talking about writing libraries that abstract across these differences and provide a single API, as sibling describes. I already know it's possible. I made a simple filesystem abstraction here[0] and a very simple HTTP library that uses it here[1]. They both work in Node/Deno and the browser. Unfortunately I ran into issues with Bun's slice implementation[2]. But I suspect there's a much better way of detecting and using the different backends.
[0]: https://github.com/waygate-io/fs-js
[1]: https://github.com/waygate-io/http-js
[2]: https://github.com/oven-sh/bun/issues/7057
What are some alternatives?
vite - Next generation frontend tooling. It's fast!
esbuild - An extremely fast bundler for the web
GORM - The fantastic ORM library for Golang, aims to be developer friendly
terser - ๐ JavaScript parser, mangler and compressor toolkit for ES6+
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
mocha-esbuild - Run tests with mocha compiled by esbuild
fastify - Fast and low overhead web framework, for Node.js
fjb - fast javascript bundler :package:
go-pg - Golang ORM with focus on PostgreSQL features and performance
source-map-explorer - Analyze and debug space usage through source maps
deno - A modern runtime for JavaScript and TypeScript.