Skip to content

feat: use nuxt-site-config module if available for origin extraction#501

Open
astraldev wants to merge 1 commit intoatinux:mainfrom
astraldev:feat/use-site-config-if-present
Open

feat: use nuxt-site-config module if available for origin extraction#501
astraldev wants to merge 1 commit intoatinux:mainfrom
astraldev:feat/use-site-config-if-present

Conversation

@astraldev
Copy link
Copy Markdown

Fixes #500

I've added an extra plugin to check if nuxt site config is available, and use it's getNitroOrigin composable at the getOAuthRedirectURL method

@atinux
Copy link
Copy Markdown
Owner

atinux commented Feb 13, 2026

Not sure I am happy with this approach, most people use the NUXT_PUBLIC_SITE_URL env variable, worst case we can read from it

@astraldev
Copy link
Copy Markdown
Author

Understandable, if the module itself can have support for a base url, then there would be no need for it. I picked it since the getNitroOrigin is a well feature packed utility.

Would you prefer I clone it instead (only the relevant part)? So we don't rely on that?

It's quite strange, we have to configure the redirect url for each oauth provider manually.

Using the NUXT_SITE_PUBLIC_URL would still mean having to manually configure each of them again since the guess method doesn't really do so well

Copy link
Copy Markdown
Owner

atinux commented Feb 17, 2026

But my main concern is why the current behavior does not work for you @astraldev?

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

Successfully merging this pull request may close these issues.

[FEATURE]: Better integration for redirect urls

2 participants