Improve missing and invalid key error messages
Updated error messages for missing and invalid Clerk keys to recommend using the Clerk CLI for key management, including init, env pull, and deploy commands. This improves the user experience when keys are misconfigured or unavailable.
Patch Changes
- Update missing and invalid key error messages to recommend the Clerk CLI:
npx clerk@latest init(non-interactive, no Clerk account required) to create an application,npx clerk@latest env pullto fetch the keys of an existing one, andnpx clerk@latest deploy/npx clerk@latest env pull --instance prodfor production. This covers both theerrorThrowermessages and the errors thrown byparsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a barePublishable key not valid.The Dashboard link is kept for manual key copying. (#9491) by @djgould
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.