#Remix Auth's GitHubStrategy v3.0.0

1 messages · Page 1 of 1 (latest)

late imp
#

I just released the v3.0.0 of the GitHubStrategy for Remix Auth v4

This release now uses Arctic's OAuth2 client for GitHub which is a specialized client instead of a generic one.

It also stops fetching the user profile from GitHub, you can do it if you want and the README contains instructions on how to fetch it, same for the list of emails of the user.

https://github.com/sergiodxa/remix-auth-github/releases/tag/v3.0.0

GitHub

This release upgrade the package to use Remix Auth v4 which means it now works on Remix and RRv7.
This release contains a breaking change in the options the strategy receives, and internally it now...

primal crater
#

Thankyou Sergio ❤️
Is it possible to create some universal like client = Google / Facebook? Since we are using arctic?

late imp
#

The OAuth2 one, but the client doesn’t support providers that are not spec compatible, like GitHub

wraith skiff
#

Why are you using Arctic? And what does it mean not to fetch the user profile? Isn't that just "part of" the OAuth flow?

i.e., what does it mean to use Arctic over GH?

late imp
#

And no, fetching the user profile is not part of the OAuth flow

#

The flow ends once you exchange the code for an access token

#

Then it’s up to you to fetch the user profile using that token

#

If for example you’re only linking GH with an already logged in user you may not need it

#

Regarding your last question, it’s not Arctic or GH, I just use a lib that implements an OAuth client compatible with GH so I don’t have to