Add bechmarks for chalk 5 and yoctocolors #61
Conversation
prantlf
force-pushed
the
chalk5-yoctocolors-benchmarks
branch
3 times, most recently
from
d37a6a6
to
1cd18ec
Compare
The latest version of `chalk` does not support CJS, but it is possible to bundle it in the CJS format. It is worth testing the latest available version. `yoctocolors` does not support CJS, but it is possible to bundle it in the CJS format. This library aspires to be the new tiniest one. It supports `FORCE_COLOR` and `NO_COLOR` too. It is worth comparing it to `picocolors`. Split `chalk` to `chalk4` and `chalk5` using NPM module aliases. Also upgrade development dependencies. Keep the same major version of `clean-publish` not to break the legacy Node.js tests. Use `esbuild` to create CJS bundles of `chalk5` and `yoctocolors`. Add `chalk5` and `yoctocolors` to every benchmark. Rename the former `chalk` tests to `chalk4`. Correct the number formatting to allow one more decimal place.
prantlf
force-pushed
the
chalk5-yoctocolors-benchmarks
branch
from
1cd18ec
to
e50360d
Compare
Copy the `simple` and `complex` benchmarks and convert the module-importing code. Use the dynamic import to measure the loading time of ESM modules. The `--esm` argument enables the ESM mode.
It does not support NPM package aliases needed for tests of `chalk` 4 and `chalk` 5. It could be worked around by an additional `package.json`, but it is probably not worth the effort.
|
Thank you for taking time to contribute! I will need a bit more time to thoroughly review the changes, apologies for the delay. The very least I can say is that the decision to drop Node.js v6 should not be in the scope of this PR. This is something better be done in a separate PR and dropping anything below v10.16 would allow us to simplify color detection by a lot. Most likely a breaking change, so we gotta check if the largest user would be okay with it moving forward cc @ai Another thing I'd like to point out is that 
Let's remove yoctocolors from benchmarks. |
Browserslist supports Node.js 6 and releasing new major is very painful for the project. But I think I can just avoid requiring |
It is now: https://github.com/sindresorhus/yoctocolors/releases/tag/v2.0.1 |
Fixes #45.
Changes
The latest version of
chalkdoes not support CJS, but it is possible to bundle it in the CJS format. It is worth testing the latest available version.yoctocolorsdoes not support CJS, but it is possible to bundle it in the CJS format. This library aspires to be the new tiniest one. It supportsFORCE_COLORandNO_COLORtoo. It is worth comparing it topicocolors.Split
chalktochalk4andchalk5using NPM module aliases. Also upgrade development dependencies. Keep the same major version ofclean-publishnot to break the legacy Node.js tests.Use
esbuildto create CJS bundles ofchalk5andyoctocolors. Addchalk5andyoctocolorsto every benchmark. Rename the formerchalktests tochalk4.Results
The
simple.jsbenchmark shows 5% decrease of performance inchalk5 againstchalk4.yoctocolorsbeatpicocolorsby 284%.The
complex.jsbenchmark shows 3% decrease of performance inchalk5 againstchalk4.yoctocolorsbeatpicocolorsby 61%.The
loading.jsbenchmark shows 44% decrease of performance inchalk5 againstchalk4.yoctocolorsis 75% slower thanpicocolors. I tried replacing the color detection inyoctocolorswith the code frompicocolorsand the loading time went down to 0.588 ms, 52% slower thanpicocolors.The
size.jsbenchmark shows 57% size reduction forchalk5 againstchalk4.yoctocolorsis practically the same aspicocolors. This benchmark isn't reliable, because the size of the actually used code may be much smaller, as the comparison of the single-file librariesyoctocolorsandpicocolorsshows.