Fix route matching when Next.js trailingSlash is enabled #1948
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.
Fix route matching when Next.js trailingSlash is enabled (#1938)
Fixes #1938
Problem
When using
trailingSlash: true
innext.config.js
, the SDK's authentication routes (login, logout, etc.) returned 404 errors due to strict path comparisons that didn't account for trailing slashes.Solution
Normalize pathnames before route matching:
removeTrailingSlash
utility to consistently handle pathspathUtils.ts
for better maintainabilityKey Changes
This ensures routes work correctly regardless of Next.js'
trailingSlash
configuration, without breaking existing implementations.