Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For future development of this library #205

Open
aiji42 opened this issue Jul 10, 2022 · 1 comment
Open

For future development of this library #205

aiji42 opened this issue Jul 10, 2022 · 1 comment

Comments

@aiji42
Copy link
Owner

aiji42 commented Jul 10, 2022

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.

@BigDog1400
Copy link

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 ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants