You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will divide and reduce with respect to future development of this library.
In order to reduce maintenance costs, I discontinue features that are not widely used, can be substituted by other libraries, or are undesirable to solve with middleware.
ip: Split as next-fortress/ip
firebase: Split as next-fortress/firebase
auth0: Abolish. (It is undesirable to solve with middleware)
cognito: Abolish. (Use next-auth)
This work will be done after Next.js v12.2 support (#200). This means that features marked as abolish will at least be supported in Next.js v12.2, but not later.
The text was updated successfully, but these errors were encountered:
Hi. I was trying to use this package with cognito, but it's implementation is outdated, nevertheless i took the source code and implemented in my own project with the updated version, i was thinking about making a PR to update this package but then i found out this issue.
I think that this package has a place for cognito, for example you can't use a custom UI with cognito while using next-auth. And currently the aws-amplify library doesn't work with the nextjs middleware to handle session validations ( and who knows how many months will be needed for their to fix it ).
I will divide and reduce with respect to future development of this library.
In order to reduce maintenance costs, I discontinue features that are not widely used, can be substituted by other libraries, or are undesirable to solve with middleware.
next-fortress/ip
next-fortress/firebase
This work will be done after Next.js v12.2 support (#200). This means that features marked as abolish will at least be supported in Next.js v12.2, but not later.
The text was updated successfully, but these errors were encountered: