The basic ideas of nanoutils:
- Functional programming is awesome 🔥
- No dependencies ❌
- No ES6 features ❌
- Efficient ⚡🚀
- Light 🎈
Awesome size 📦
Size is important as download time depends on it
nanoutils uses SIZES.md to check its size.
According to recently added statistics:
nanoutilsmethods are less than
ramdahas its median around
- maximum method size for
ramdadoesn’t limit its size and its largest method equals
Based on BundlePhobia:
nanoutilsis tree-shakeable as
500msless time to be downloaded in comparison with
Performance is difficult to compare as time is different for different devices.
nanoutils uses TIMES.md to check its performance time
We use approach with Performance Timing API. We have custom CLI as well with bunch of functions and helpers which combine data and compare it based on several runs. For some methods performance tests (i.e. ap.performance.js) are written where data is cached in JSON files.
Now not all methods are covered with performance tests. It will be done in future releases.
- Idea of the project — Anton Kosykh
- Size compressor of the project — Alexey Berezin
- Performance accelerator of the project — Aleksandr Babkin
- Designer of the logo — Phil Murphy