Library size as benchmark

[beeing]

Very informative benchmark, however it will be helpful if comparison of lib sizes are taken into account.

[ebdrup]

That's a good idea. Pull Requests are welcome.

Den 16. aug. 2017 kl. 03.09 skrev Bee Ing [email protected]:

Very informative benchmark, however it will be helpful if comparison of lib sizes are taken into account.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[korzio]

@beeing That's a nice proposal. Do you think it will be a whole package size? Because yes, of course it matters, but mostly for browser.

[beeing]

Before hand, let’s use this issue to track some numbers.

All numbers below are based in current NPM installs.

AJV 267K ajv.bundle.js 117K ajv.min.js 134K ajv.min.js.map 217K nodent.min.js 949K regenerator.min.js

djv 17K djv.js 103K djv.js.map

is-my-json-valid 16K index.js 444B require.js

Need time to go through each but I think better to use a script to programmatically.

I found this library import-cost to calculate the size.

Also, would be ideal to indicate whether the library support tree-shaking or import optional parts to further reduce the library size.