Official Javascript repository for Clerk authentication
MIT License
Published by clerk-cookie 4 months ago
Published by clerk-cookie 4 months ago
427fcdeaa
]:
Published by clerk-cookie 4 months ago
427fcdeaa
]:
Published by clerk-cookie 4 months ago
427fcdeaa
]:
Published by clerk-cookie 4 months ago
427fcdeaa
]:
Published by clerk-cookie 4 months ago
Published by clerk-cookie 4 months ago
Ensure client cookie URLs resolve appropriately (#3658) by @tmilewski
Updated dependencies [427fcdeaa
]:
Published by clerk-cookie 4 months ago
f1847b70b
]:
Published by clerk-cookie 4 months ago
f1847b70b
]:
Published by clerk-cookie 4 months ago
Add backup_code
verification strategy (#3627) by @tmilewski
<SignIn.Step name='choose-strategy'>
<SignIn.SupportedStrategy name='backup_code'>Use a backup code</SignIn.SupportedStrategy>
<SignIn.Step>
<SignIn.Step name='verifications'>
<SignIn.Strategy name='backup_code'>
<Clerk.Field name="backup_code">
<Clerk.Label>Code:</Clerk.Label>
<Clerk.Input />
<Clerk.FieldError />
</Clerk.Field>
<Clerk.Action submit>Continue</Clerk.Action>
</SignIn.Strategy>
<SignIn.Step>
Addresses the issue where sign-in factors were not properly falling back to empty arrays. (#3647) by @LauraBeatris
Refactors sign-up loading logic to be in-line with sign-in (#3648) by @tmilewski
Ensure Sign Up resending resets upon being triggered (#3652) by @tmilewski
Fixes persistent loading states within the forgot-password
step (#3648) by @tmilewski
Fix Sign In forgot-password step not rendering (#3653) by @tmilewski
Published by clerk-cookie 4 months ago
Introduces dynamic keys from clerkMiddleware
, allowing access by server-side helpers like auth
. Keys such as signUpUrl
, signInUrl
, publishableKey
and secretKey
are securely encrypted using AES algorithm. (#3525) by @LauraBeatris
secretKey
, CLERK_ENCRYPTION_KEY
is required as the encryption key. If secretKey
is not provided, CLERK_SECRET_KEY
is used by default.clerkClient
from @clerk/nextjs
should now be called as a function, and its singleton form is deprecated. This change allows the Clerk backend client to read keys from the current request, which is necessary to support dynamic keys.For more information, refer to the documentation: https://clerk.com/docs/references/nextjs/clerk-middleware#dynamic-keys
f1847b70b
]:
Published by clerk-cookie 4 months ago
Published by clerk-cookie 4 months ago
Introduces dynamic keys from clerkMiddleware
, allowing access by server-side helpers like auth
. Keys such as signUpUrl
, signInUrl
, publishableKey
and secretKey
are securely encrypted using AES algorithm. (#3525) by @LauraBeatris
secretKey
, CLERK_ENCRYPTION_KEY
is required as the encryption key. If secretKey
is not provided, CLERK_SECRET_KEY
is used by default.clerkClient
from @clerk/nextjs
should now be called as a function, and its singleton form is deprecated. This change allows the Clerk backend client to read keys from the current request, which is necessary to support dynamic keys.For more information, refer to the documentation: https://clerk.com/docs/references/nextjs/clerk-middleware#dynamic-keys
Published by clerk-cookie 4 months ago
f1847b70b
]:
Published by clerk-cookie 4 months ago
f1847b70b
]:
Published by clerk-cookie 4 months ago
<Strategy>
component that isn't activated for their Clerk instance. As this can be intended behavior (e.g. build out a full example and let user enable/disable stuff solely in the dashboard) the warning can safely be ignored if necessary. (#3609) by @LekoArts
Published by clerk-cookie 4 months ago
Correctly use updated protocol verification in all code paths (#3605) by @LekoArts
Updated dependencies [72888323b
]:
Published by clerk-cookie 4 months ago
2bef41ab0
]:
Published by clerk-cookie 4 months ago
Published by clerk-cookie 4 months ago
Improve <FieldState>
and re-organize some data attributes related to validity states. These changes might be breaking changes for you. (#3594) by @LekoArts
Overview of changes:
<form>
no longer has data-valid
and data-invalid
attributes. If there are global errors (same heuristics as <GlobalError>
) then a data-global-error
attribute will be present.<Field>
could contain data-valid
and data-invalid
at the same time.<FieldState>
) now also incorporates the field's ValidityState into its output. If the ValidityState
is invalid, the field state will be an error
. You can access this information in three places:
<FieldState>
data-state
attribute on <Input>
<Field>{(state) => <p>Field's state is {state}</p>}</Field>
Fix Sign In & Sign Up root fallbacks not rendering as expected (#3601) by @tmilewski
Update all Radix dependencies to their June 19, 2024 release (#3606) by @LekoArts