Support exports.*.browser

[ai]

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:

{
  "name": "@sitnik/nanoid",
  "version": "5.1.0",
  "license": "MIT",
  "exports": {
    ".": {
      "browser": "./index.browser.js",
      "default": "./index.js"
    }
  }
}

[BlackAsLight]

On a side question: why would you write code for size at the penalty of performance? Is the small difference in size worth the hit to performance?

[ai]

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.

[realhydroper]

Related: #964