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
We still have a difference between Node.js and browser environment.
For instance, in Nano ID we need to use special Node.js API. Also Node.js and browser versions have different optimization strategies—one is for size, other is for performance.
why would you write code for size at the penalty of performance?
Because loading performance affect overall performance more in browser (when people load website multiple times per day just for few minutes) than Node.js (when we have a server running whole day, so we need to load it once).
Is the small difference in size worth the hit to performance?
Loading time difference is similar to performance losses. So it is like one to one exchange.
We still have a difference between Node.js and browser environment.
For instance, in Nano ID we need to use special Node.js API. Also Node.js and browser versions have different optimization strategies—one is for size, other is for performance.
So we need support for
exports
like:The text was updated successfully, but these errors were encountered: