`map` performance is no longuer a problem ?
Is this one able to have the same feature than Vibrant ? http://jariz.github.io/vibrant.js/
Vibrant is cool but pretty fat :/
At the beginning, it was the first argument.
But I looked more closer à my uses cases and the `console.log` API.
`console.log` could be used that way :
console.log("The awesome value is : %s", value)
And I watched at the use of the comma operator. And, I have choosen to follow the comma operator evaluation.
That said the last value of the operation will be returned.
const a = () => (add = 1 + 2, add * 3)
const a = () => log(add = 1 + 2, add * 3)
Both will return 9. And every step of the comma operation will be printed.
Author here, I permit myself (not against the rules ?) to promote my first try to create an utility function using Typescript, Jest with size and perf concerns.
A word about performance ?
Another contrib, less exotic than the first one, I did :
Do you remember that fact ?
So, here is my contribution :
After just moving to yarn, it's now time to consider moving to pnpm. Is this the thing formally known as JS fatigue ?
Does this kind of discussions have really their place here ?
Awe. Osom inspire me a lot of thing regarding Firebase pre-save schemas validation.
I will keep eyes on it ! :)