David Burles

@soofstad I have data fetching logic that lives outside of React context which relies on the access token. Currently to get the token I am grabbing it directly from local...

The only use case I have found so far is getting at the access token. The simplest approach I can think of would be to export a function that optionally...

Another use case is to be able to trigger login again if a fetch response comes back with a 401 (similar to `onRefreshTokenExpire`), which can occur if the token is...

Just another idea. Rather than periodically updating the `accessToken`, instead there should be API exported that can be called prior to data fetching. This can handle checking token expiration (and...

This looks amazing. @ije it's similar to what you mentioned here https://github.com/esm-dev/esm.sh/discussions/595#discussioncomment-9977163 a while back. Will the build command support the same package parameters as the CDN? and how will...

While comments like that can be spammy to maintainers, it's not the fault of those leaving them! The intent of those comments is to highlight that the issue should be...

> The new published version provides access to a `graphql-query-complexity` for both CJS and ESM. If the default import does not work because your other modules import a different GraphQL...

Hey thanks for taking the time to test on earlier versions of Meteor. I'm happy with the version changes. Did you want to investigate async helpers?

Great. I don't imagine it would require any changes to the source to support them. It's more a matter of including some tests for Meteor 3.

I don't have any idea on how Meteor 3 works with non async queries. Where you have commented out a test with a todo it would be good to add...