size-limit VS chartist

However, you can use the Size Limit library to control the size of a bundle or individual exports. Here’s an example configuration:

It's always good to keep track of these things over time so performance doesn't slide. Parcel, which I used for this project, has a helpful bundle analyzer (similar to the one for Webpack) that gives a nice visual overview of a project's bundle. This is especially helpful for identifying bundled dead code coming from packages that could be avoided with tree-shaking. There are also plenty of tools you can integrate with CI to enforce bundle size.

TSDX is a great package for npm packages like this and even bundles with size-limit to check your gzipped final bundle size. Keeping a tiny package was really important to me so there are 0 dependencies and size-limit made me realise that simplifying all of my checking functions into 1 or 2 core functions that took options would be a better strategy and help reduce the code size.

Small. 130 bytes (minified and gzipped). No dependencies Size Limit controls the size.

Size Limit is a performance budget tool for JavaScript. It checks every commit on CI, calculates the real cost of your JS for end-users, and throws an error if the cost exceeds the limit. Link: https://github.com/ai/size-limit

-Mark Erikson and Joel Hooks talk on Redux -When and when not to reach for Redux -Redux Introduction -Egghead course by Dan Abramov on Fundamentals of Redux -RDD article by Tom Preston Werner -Another Article on RDD -Article on writing a great Readme -RDD Readme Example: size-limit

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.)