Switch to mri and yoctocolors for better performance?

[so1ve]

I can contribute to this:)

[haoqunjiang]

• For argument parsing, I prefer to switch to the built-in util.parseArgs https://nodejs.org/dist/latest-v20.x/docs/api/util.html#utilparseargsconfig Maybe we can do it after Node.js v16 reaches End-of-Life so that dropping older Node.js versions won't surprise too many users.
• As for yoctocolors, it lacks conventional environment variables support (e.g. those listed at https://github.com/marvinhagemeister/kolorist#usage, plus CI, etc.; those are commonly respected environment variables in most other color libraries)

[so1ve]

Actually yoctocolors supports environment variables. They are handled in tty.WriteStream.prototype.hasColors (a built-in node module)!

[so1ve]

And for now we can switch to mri for smaller size because util.parseArgs is still unstable.

[haoqunjiang]

Actually yoctocolors supports environment variables. They are handled in tty.WriteStream.prototype.hasColors (a built-in node module)!

Thanks for the info! Good to know that. Then I'm not against switching to yoctocolors.

However, I just did some research and found that picocolors is both smaller and more popular than yoctocolors. Maybe that's a better alternative?

https://packagephobia.com/result?p=picocolors
https://packagephobia.com/result?p=yoctocolors
https://npmtrends.com/picocolors-vs-yoctocolors

[haoqunjiang]

And for now we can switch to mri for smaller size because util.parseArgs is still unstable.

It is stable in Node.js 20, and the API isn't much different from what has been implemented in v16 and v18.

Considering we will switch to it eventually, I don't feel like migrating to mri for the marginal improvement in package sizes. Reviewing PRs also takes time.

[so1ve]

Actually yoctocolors supports environment variables. They are handled in tty.WriteStream.prototype.hasColors (a built-in node module)!

Thanks for the info! Good to know that. Then I'm not against switching to yoctocolors.

However, I just did some research and found that picocolors is both smaller and more popular than yoctocolors. Maybe that's a better alternative?

https://packagephobia.com/result?p=picocolors https://packagephobia.com/result?p=yoctocolors https://npmtrends.com/picocolors-vs-yoctocolors

Maybe…? However yoctocolors seems to have better performance. Benchmark later :)

[haoqunjiang]

Why does performance matter in the use case of create-vue? There are only a few calls to the color functions; the difference might be only a few μs.

[so1ve]

Why does performance matter in the use case of create-vue? There are only a few calls to the color functions; the difference might be only a few μs.

Makes sense. Let's switch to picocolors!

[haoqunjiang]

I eventually switched to kleur/colors in 0395555
Because turns out it produces the smallest bundle for our usage…