Grant Wu

I feel like that would make it sound like something where you attach an event handler, instead of what it actually does. Also, I don't think this is a good...

https://github.com/apollographql/graphql-subscriptions/blob/master/.designs/authorization.md does this help at all? It's a very old doc, unfortunately I don't really know much about this topic.

Keeping this open because it seems like we could use more documentation on this.

Has there been any movement on this? Using `cross-fetch` seems like a strange workaround since it just uses `node-fetch`. Is that not actually a problem? `whatwg-fetch` is not a workaround...

You can just use an `as` type coercion thing...

Sorry, I misread what you were doing, ignore my previous comment. However, this requires you modify your tsconfig to target the browser, as GlobalFetch is only provided if you have...

1. Ah, I didn't realize that was required. TIL. 2. Sorry, I'm just having a really off day. You're right, that's a type, not a variable. https://www.npmjs.com/package/whatwg-fetch states pretty explicitly...

Upon further review, this seems to be mainly a problem with `node-fetch`, so I opened the above issue. It's entirely possible that they will tell us to just change our...

Okay, `node-fetch` seems to be telling us to just change our types. One hack would be to import `node-fetch`'s types and to add that as a workaround?

It's still not working for me :/ ``` src/remoteSchemas.ts:54:45 - error TS2322: Type '(input?: RequestInfo, init?: RequestInit) => Promise' is not assignable to type '(input: RequestInfo, init?: RequestInit) => Promise'....