nextauthjs / nextauthjs/next-auth
Frontegg provider listed in docs but not available in module
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28.4k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
What is the improvement or update you wish to see?
The Frontegg provider is listed in next-auth's documentation, but doesn't seem to be available in the current releases of the module on NPM.
Should the docs be updated with a timeline on when this provider will be made available / which version should be used? Or is there a way to use that provider in the meantime?
Is there any context that might help us understand?
It looks like the provider was first added back on December 21, but the last NPM release was December 6 (and for the beta release even further, September 19).
Does the docs page already exist? Please link to it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the auth.dev Frontegg provider page with the current next-auth releases on NPM and the provider's addition in the repository history. Determine whether the documentation should identify a release/version or explain interim usage; done means the page and release guidance accurately match provider availability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- authentication, documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100