@clerk/chrome-extension/legacy is missing from package exports

[kritikmodi]

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

N/A

Publishable key

N/A

Description

The legacy useSignIn() and useSignUp() documentation includes Chrome Extension examples that import from @clerk/chrome-extension/legacy:

• https://clerk.com/docs/reference/hooks/legacy/use-sign-in
• https://clerk.com/docs/reference/hooks/legacy/use-sign-up

import { useSignIn } from '@clerk/chrome-extension/legacy'
import { useSignUp } from '@clerk/chrome-extension/legacy'

I reproduced this with @clerk/chrome-extension@3.1.69 and TypeScript 5.9.3.

Steps to reproduce

npm install @clerk/chrome-extension@3.1.69 typescript react react-dom

Create index.ts:

import { useSignIn, useSignUp } from '@clerk/chrome-extension/legacy'

export { useSignIn, useSignUp }

Run:

npx tsc --noEmit \
  --module NodeNext \
  --moduleResolution NodeNext \
  --target ES2022 \
  --jsx react-jsx \
  --skipLibCheck \
  index.ts

Actual behavior

TypeScript reports:

error TS2307: Cannot find module '@clerk/chrome-extension/legacy' or its corresponding type declarations.

The published package export map does not contain a ./legacy entry.

Expected behavior

Either:

1. @clerk/chrome-extension/legacy should be exported so the documented examples compile, or
2. Chrome Extension should be removed from the SDK scope of these legacy reference pages if the legacy API is not intended to be supported.

Environment

N/A

[wobsoriano]

thanks for reporting! Fixing here #9434