We've refactored our API keys to a more familiar format:
pk_test_ or pk_live_)sk_test_ or sk_live_)With this upgrade, we introduced a quick copy in our dashboard for each of our SDKs allowing you to move faster than ever.
Legacy keys are still available in the dashboard and can continue to be used. Once ready to upgrade, you will need to replace all the keys simultaneously, as you cannot mix the legacy keys with the new ones.
Learn more about the motivation behind our new keys.
Developer experience is huge for us here at Clerk, and with that, we want to make it easy to get started and easier to find what you are looking for.
Last week we introduced new environment-driven examples, allowing us to insert your keys into our docs. This is only in our get-started sections, but we want to add it to more places in the near future.
We spent some time improving the search and results that were returned, this has been high on our list this month, and we think the improvement already shows.
We launched a new starter repo called t3-turbo-and-clerk.
For the launch, we collaborated with t3's creator, Theo Browne, to show off the simplicity of the solution. Check it out:
We updated our Gatsby plugin to support Gatsby V5. You can now access the user's authentication state on the client or the server. Below are examples of SSR and API routes:
We now support migrating users and their hashed passwords (using pbkdf2_sha1) from RedwoodJS dbAuth to Clerk using our API.
Migrating for another tool? Contact support to let us know if you need us to add another hashing algorithm.
We have dropped support for Node 12 and will be only supporting Node 14 or higher.
A massive shoutout to Darlan for his first contribution to Clerk by adding a Brazilian translation to our Clerk components.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。