Update to browser.js

[justjish]

Helps to prevent an issue when this code is bundled using Rollup.

[sindresorhus]

Can you link to the Rollup issue in their issue tracker?

[Qix-]

Suggested change

	const isBlinkBasedBrowser = typeof navigator !== 'undefined' ? /\b(Chrome|Chromium)\//.test(navigator.userAgent): false;
	const isBlinkBasedBrowser = typeof navigator !== 'undefined' && /\b(Chrome|Chromium)\//.test(navigator.userAgent);

[Qix-]

The RHS of the : in a ternary is implicitly the false case, so this can be simplified as such - namely that the short-circuit will result in a false and RegExp.prototype.text() returns a boolean.

[Trott]

Can you link to the Rollup issue in their issue tracker?

I don't believe there is an issue in the issue tracker for this. I don't think it's a bug (although it is surprising behavior, at least to me).

@sujishpatel I believe this is an issue with @rollup/plugin-node-resolve. By default, it will use the "default" export over the "node" export. For this module, the default export is browser.js which is not intended to work in Node.js. The docs for @rollup/plugin-node-resolve say to set the exportConditions option to ['node'] if you want the resolution behavior of Node.js. That config change fixed the issue for me. I would expect that to be the default behavior with that plugin, but I do not know the full context around the decision to do otherwise, so maybe there is an excellent reason for it. In any event, to get that behavior, use nodeResolve({exportConditions: ['node']}) instead of just nodeResolve() in your rollup config. That fixed the issue for me.