nextjs - 💡(How to fix) Fix Update docs to reflect omission of `NEXT_` prefix. And everything else. And stop, please. [1 comments, 2 participants]

Link to the code that reproduces this issue

https://authjs.dev/getting-started/installation?framework=Next.js

To Reproduce

Update docs to reflect omission of NEXT_ prefix *its all over the place. And you dont know which version its referring to. Please maintain consistency and push for relevance in your docs. I have to be honest. I've never spent longer on anything in 22yrs of my career than trying to understand a single piece of tech with such insanely abstract references to usages without any context applied (such as 'usage: some async operation' without any guidance around whether that's a component level thing, client component, server, onClick event etc). Lacking paramounts of context and especially dying at the oAuth end. Zero follow through on cookie usage for oAuth, JWT necessities--which happen to be required regardless of the even more bloated crossover with next-auth-better-auth-but-not-totally-better-auth-but-is--move to get any scoped API data back. I have wasted over a year just on NextJS and that's because i like things being in an 'app' folder. That's it. I'm only writing this as a courtesy that to any new devs or even intermediate, this is hell. And it's gotten worse with every new partner merge and update. Thanks,

Current vs. Expected behavior

get data back from linkedin auth via next auth + supabase then display it on a page.

Provide environment information

all environments

Which area(s) are affected? (Select all that apply)

Dynamic Routes

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response