Fix incorrect deprecation warning for afterSignInUrl / afterSignUpUrl in ClerkProvider

[tonton-k37]

Preliminary Checks

• I have reviewed the documentation: https://clerk.com/docs

• I have searched for existing issues: https://github.com/clerk/javascript/issues

• I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

• This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction

javascript/packages/types/src/redirects.ts

Line 23 in 377f67b

* @deprecated Use `fallbackRedirectUrl` or `forceRedirectUrl` instead.

Publishable key

pk_test_cmVmaW5lZC1tYW4tNzIuY2xlcmsuYWNjb3VudHMuZGV2JA

Description

Steps to reproduce:

1. Set up ClerkProvider in a Next.js project using afterSignInUrl or afterSignUpUrl props
2. Run the app and check the console warnings.

<ClerkProvider 
  publishableKey={process.env.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY}
  afterSignInUrl="/dashboard"
  afterSignUpUrl="/dashboard"
>

Expected behavior:

• The deprecation warning should suggest the correct replacement props:
• signInFallbackRedirectUrl
• signUpFallbackRedirectUrl

Actual behavior:

• The current warning suggests: Use fallbackRedirectUrl or forceRedirectUrl instead.
• These props do not exist, which makes it unclear what to replace with.
• The correct replacement is signInFallbackRedirectUrl / signUpFallbackRedirectUrl.

If this is confirmed, I’m happy to open a PR to fix the deprecation warning message so it points to the correct props.

Environment

System:
- OS: windows 11
Binaries:
- Node: v22
Browsers:
- Chrome: 139.0.7258.139
npmPackages:
- clerk/nextjs: 6.29.0

[wobsoriano]

Thanks for reporting! Fix should be available in the next release. In the meantime, you can install a snapshot of your SDK of choice here - #6699 (comment)