You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was comparing it with other alternatives like esprima and espree.
From what I found, esprima & espree have lot of features but have smaller Unpacked size as reported by npm.
It is relatively faster, but considering the small scope of it's features, I don't think that performance gain is beneficial. (Like if we have to run small expressions, then every library does it within 20ms and 10-20ms is not big gain).
I think that npm reports unpacked size of all files in package (not only executable code). jsep ships with 3 different bundles (commonjs, iife, module) and sourcemaps for this
I was comparing it with other alternatives like esprima and espree.
From what I found, esprima & espree have lot of features but have smaller Unpacked size as reported by npm.
It is relatively faster, but considering the small scope of it's features, I don't think that performance gain is beneficial. (Like if we have to run small expressions, then every library does it within 20ms and 10-20ms is not big gain).
For reference,
benchmark code
After this, I became curious to know what is the selling point of jsep and why/when should one prefer it over others ?
The text was updated successfully, but these errors were encountered: