the `routing=virtual` in `<SignIn />` component removed is A BREAKING CHANGE which casue our app build failed

[arvinxx]

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

code below:

import { ClerkLoaded, ClerkLoading, SignIn } from '@clerk/nextjs';
import { memo, useState } from 'react';

import Notification from '@/components/Notification';
import Loading from '@/features/User/LoginNotification/Loading';

const LoginNotificationModal = memo<LoginNotificationModalProps>(({ variant }) => {
 const [show, setShow] = useState(true);
 const isAtTop = variant === 'top';

 return (
 <Notification
 onCancel={() => setShow(false)}
 show={show}
 >
 <ClerkLoading>
 <Loading atTop={isAtTop} />
 </ClerkLoading>
 <ClerkLoaded>
 <SignIn routing={'virtual'} />
 </ClerkLoaded>
 </Notification>
 );
});

export default LoginNotificationModal;

Publishable key

none

Description

I notice #4977 this pr remove the virtual props, which cause our product build failed.

I really don't the routing=virtual props is an internal value, you have just write it on the document but just remove it within a patch version. It's horrible.

Here is our usage with this routing=virtual, if you just remove this props, how can we achieve the same feature without it?

please consider to turn back this props, or remove it in the next Major version and give out a migration guide.

Steps to reproduce:

Expected behavior:

not build error

Actual behavior:

cause an error of ts error:

src/features/User/LoginNotification/Notification.tsx:77:51 - error TS2322: Type '"virtual"' is not assignable to type '"path" | "hash" | undefined'.

77 <SignIn appearance={{ elements: styles }} routing={'virtual'} />
 ~~~~~~~

 node_modules/.pnpm/@clerk+types@4.44.2/node_modules/@clerk/types/dist/index.d.ts:4824:5
 4824 routing?: Extract<RoutingStrategy, 'path'>;
 ~~~~~~~
 The expected type comes from property 'routing' which is declared here on type 'IntrinsicAttributes & Without<WithClerkProp<SignInProps & FallbackProp>, "clerk">'

Environment

System:
 OS: macOS 15.2
 CPU: (10) arm64 Apple M1 Max
 Memory: 73.48 MB / 64.00 GB
 Shell: 5.9 - /bin/zsh
 Binaries:
 Node: 22.11.0 - /usr/local/bin/node
 Yarn: 1.22.19 - ~/Library/pnpm/yarn
 npm: 9.2.0 - ~/Library/pnpm/npm
 pnpm: 9.15.4 - ~/Library/pnpm/pnpm
 bun: 1.0.26 - ~/Library/pnpm/bun
 Browsers:
 Brave Browser: 127.1.68.128
 Chrome: 132.0.6834.111
 Chrome Canary: 134.0.6983.0
 Safari: 18.2

[arvinxx]

now I have overrides the @clerk/types to 4.44.1, hope you can revert the change or give a migration way to do it:

{
 "dependencies": {
 "@clerk/nextjs": "6.10.2",
 },
 "pnpm": {
 "overrides": {
 "@clerk/types": "4.44.1",
 }
 },
 "overrides": {
 "@clerk/types": "4.44.1"
 }
}

[alexcarpenter]

@arvinxx the change has been reverted. Apologies for the inconvenience. Virtual routing uses hash under the hood, so we wanted to make sure it was obvious that was happening. We've marked as deprecated and will wait to remove until the next major release.

#5057

[arvinxx]

@alexcarpenter hi, thanks for the quick response. But in my usage show above, what's the correct migration way to the hash routing?

we don't want to have a login or signup hash url explicitly, so we use the virtual routing.

[alexcarpenter]

Currently virtual routing is just making use of hash routing internally. Which is what let us to make the type change. In your usage are you not seeing the URL update when moving through your sign-in flow?

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.