feat(core): add basePath configuration option#24
Merged
halvaradop merged 1 commit intomasterfrom Dec 10, 2025
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This pull request introduces the
basePathconfiguration option to the Aura instance created through thecreateAuthfunction.With this new feature, users can override Aura Auth’s default base path (
/auth) and define custom paths that better fit their application structure.Before
Route handlers were required to live under the
/authbase path, depending on the library or framework integrating Aura Auth. For example, in Next.js (App Router), users needed to place their route handler at:/app/auth/[...aura]/route.tsAfter
With the new
basePathoption, users can host and place route handlers anywhere in their backend as supported by their library or framework. In Next.js, examples now include:/app/api/auth/[...aura]/route.ts/app/api/v1/auth/[...aura]/route.ts/app/authentication/[...aura]/route.tsThis enhancement provides greater flexibility and enables seamless integration into a wider variety of backend and routing structures.