@clerk/nextjs: Missing Clerk keys now throw error instead of enabling keyless mode
Missing Clerk authentication keys (NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY) now throw an error directing developers to run npx clerk@latest init, instead of silently activating keyless mode. This improves development experience by making configuration requirements explicit. Existing apps with configured keys are unaffected.
Minor Changes
- In development, missing Clerk keys no longer activate keyless mode. When
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEYandCLERK_SECRET_KEYare not set, the SDK now throws an error directing you to runnpx clerk@latest init, which provisions a Clerk application and writes the keys to.env.local. Keyless credentials stored in the development keyless cookie are no longer read. Existing apps with configured or claimed keys are unaffected. (#9493) by @djgould
Patch Changes
Source: original entry ↗
More from Clerk
Follow Clerk to get its new changes in your feed and email digest.
@clerk/expo-native-components package introduced
A new @clerk/expo-native-components package is now required for native components (AuthView, UserButton, UserProfileView). Install it before deploying over-the-air updates as errors occur at runtime; import native components from @clerk/expo/native-components and deprecate the old @clerk/expo/native import path.
@clerk/expo-native-components 0.1.0
Introduces @clerk/expo-native-components, a new required package for native components (AuthView, UserButton, UserProfileView). Import native components from @clerk/expo/native-components instead of the deprecated @clerk/expo/native, and install the new package before shipping over-the-air updates to avoid runtime errors.
@clerk/ui@1.40.1
Release of @clerk/ui version 1.40.1 with updates and improvements to the UI component library.