Search for a command to run...
Series
In this series, I'll check how various date manipulation libraries perform in the build - especially in regards to output size.
In this article, I'll take a quick look at the build size of a simple code that imports a method from date-fns. I check results from both, webpack & esbuild. The code The code I use in this test is as follows: import { sub } from "date-fns"; const t...
In this article, I'll take a look at the size impact of importing luxon. I'll check with both webpack & esbuild. The code Similar to the date-fns article in this series, I'm testing with a rather simple code: // import trick from https://github.com/m...
In this article, I'll take a look at how much the build size increases when you add Day.js library for date object manipulation. Library Day.js is an interesting library that implements a similar API as moment.js but with a smaller overhead. Because...
In this article, I'll look at how much our application is growing when we add Moment.js. As Moment.js is not supporting tree shaking, it makes no difference if we use many or 1 methods from it. Library Moment.js is a popular but deprecated library - ...
In this article, I'll look at application size with multiple methods imported from date-fns. In the previous benchmark attempt, I was only using 1 method from each library. date-fns, as the only one built with tree-shaking in mind, enjoyed an advanta...
This article will show how to work around a small gotcha in Day.js and show the library's code for the second round of the build size benchmark. Backstory As I explained in the second article about date-fns, comparing the use of only one method skews...
