Tarik Ansari

@racheldotey I had the same question as you, and ended up using [parse-latin](https://github.com/wooorm/parse-latin) which parse text and generates an AST together with [js-traverse](https://github.com/substack/js-traverse) which is a utility library that helps...

Same issue: 

@gr2m this is unrelated to conditional exports though. You would use conditional exports where you want an import present in multiple environments -- which on that subject, is arguably no...

@jimmywarting I may be wrong on this, but I think this may not need to go beyond fetch/Headers/Request/Response. In practice, if format objects or other things are used and need...

@goya so the feature that you linked (`browser.js`), is unrelated, it's a conditional export to use `node-fetch` in the browser. which was a bad idea to start with IMO. `node-fetch`...

You probably shouldn't do that though, your bundler/packaging script should allow you to handle this with entry points. This will avoid leaking abstractions, reduce your bundle size a bit, and...

Bumping this up. I expected `webpack-node-externals` to just work with PnP and it took me a while to find that this was my issue. I found two packages that implement...

@mbrevda FYI `superagent-cache` is not RFC7234 compliant. What the browser offer is caching that honors http headers, so if it's implemented on the server side, it would make sense to...

@jimmywarting that's an interesting approach, I like it, however I agree with the responses on that thread, it shouldn't be necessary to implement WebWorkers to offer cache. I think the...

Sure, it's a matter of internal preference, also, while the caching logic and storage would be outside `node-fetch`, I believe hooking up the two should happen in `node-fetch` to be...