Intended usage for Browser/Nodejs agnostic libs unclear about cross-fetch HOT 3 CLOSED

@lquixada -- thanks for explaining that; this was exactly what I was looking for.

I feel you're using the same bundle for both environments: Node and Browsers.

^ This is precisely what I wanted to do -- but it looks like it isn't best practice/possible to do so.

As I understand it, I had misinterpreted 'isomorphic' to mean isomorphic during runtime, when it actually referred to isomorphic during bundle time. For my use case, since the majority of usage will come out of the browser, I'll probably look to assume a global fetch instead, and request node users to simply patch node-fetch as a global object.

Thanks!

from cross-fetch.

I feel you're using the same bundle for both environments: Node and Browsers. If that's the case you should create a webpack build specific to node using the target config. The reason for that is webpack will choose which cross-fetch entry-point it will use ("main" or "browser") depending on the target environment.

Closing this issue for now.

from cross-fetch.

I feel you're using the same bundle for both environments: Node and Browsers. If that's the case you should create a webpack build specific to node using the target config. The reason for that is webpack will choose which cross-fetch entry-point it will use ("main" or "browser") depending on the target environment.

Closing this issue for now.

There is zero documentation on how to do this. Very frustrating.

from cross-fetch.