Jason Miller

fixed in #156

I mentioned this in the PR, but `global` is not a standard. `self` is a standard - it is defined in all browser environments (document, all worker types, worklet, etc)....

I'm going to close this because it should be fixed in [isomorphic-unfetch 4.0.1](https://github.com/developit/unfetch/releases/tag/isomorphic-4.0.1) due to the addition of package exports.

@RReverser because I'm a bad person!

Alrighty, I merged this manually (had to rewrite the history). Sorry for the (checks watch) 5 year delay!

@DVSoftware That's the right way to go! Closing since IMO the `"storagechange"` event is the best option here (and you can wire it up to mitt if you need).

`off()` is only really supported by Vue IIRC, whereas this API is more in line with Node's EventEmitter. The error propagation is a good point. I will have to check...

Just wanted to re-up this to put it back on your radar @jaredpalmer. There's now a good bit of steam around the `"exports"` field implying modern JavaScript. The TLDR is...

@hardfist there is a "node" exports object key that you can use to provide a different set of exports for Node, with the other keys assumed to be browser: ```js...

Absolutely. There are a number of DOM warts that could be intentionally omitted from a layout-less threaded DOM API: - no cross-realm append / importNode - no DOM-based scripting (event...