[ Request ] Support remix-auth@v4 and RR7

[incadenza]

Hey, there. Huge fan of your work - I've been using your remix auth tools for as along as I've worked with Remix. Much gratititude.

Is there any small direction you can nudge me in to be of assistance here? I noticed this library is behind the 2.0 of the main remix-auth.

Again, many thanks. I want to help

[dev-xo]

Hello @incadenza!

First of all, thanks for the gratitude, also happy to know remix-auth-totp has been useful to you.

To be honest, I'm a bit busy lately, and neither of the latest updates on the library were handled by me. I know @sergiodxa has got remix-auth to v4, supporting RR7, and I had in mind to look into it sooner or later (although not sure when).

I wonder if he could share some little insights that may help us give support to RR7, allowing the library to continue being useful for others.

Also, wonder if @mw10013 wants to or would be able to share some thoughts on this too.

In any case, thanks for the great words, and hopefully, between us all, we could give RR7 support and keep the library useful for us and for others!

[sergiodxa]

The main change for strategies is regarding to sessions/cookies, since there's no sessionStorage anymore, you will either need to ask the sessionStorage object as an option of the strategy, or you will have to change to a cookie or use something else.

In the OAuth2Strategy and GitHubStrategy I'm using @mjackson/headers to work with cookies directly instead of using the app session storage.

Then the this.success and this.failure functions are removed, in case of success just return the result of this.verify, in case of failure throw an error yourself.

[CyrusVorwald]

I submitted a PR to be compatible with remix auth v4 by using cookies directly as per @sergiodxa's helpful response. This removed a couple tests that were checking context. See #82

[dev-xo]

Thanks @CyrusVorwald! Will review your PR and continue the discussion there. Also, thanks to @sergiodxa for the insights and the response!