Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new
docsUrlpoints to theauthkit-nextjsREADME, butCOOKIE_DOMAIN_NOT_SETis emitted wheneverreport.sdk.isAuthKitis true (line 102), which covers non-Next.js AuthKit integrations (Remix, SvelteKit, etc.). Those users will be sent to Next.js-specific instructions that may not directly apply to their setup. A first-party docs page or a more generic reference would cover the full audience, though this is still a clear improvement over a 404.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tending to agree with Greptile here. Considering that https://github.com/workos/authkit-tanstack-start et al also use these env vars what do you think about opening a docs PR for this? 😓