nextjs-supabase-auth
rfcs
nextjs-supabase-auth | rfcs | |
---|---|---|
3 | 7 | |
250 | 234 | |
- | - | |
5.9 | 0.0 | |
4 months ago | over 1 year ago | |
JavaScript | ||
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nextjs-supabase-auth
-
Authentication in Next.js with Supabase Auth and PKCE
The individual auth form components can be found in GitHub. These were built using Formik, following one of their examples in the docs. See the previous post for more details.
-
Authentication in Next.js with Supabase and Next 13
NOTE: Make sure to read the original post first if you haven't yet, as we'll be building on the main concepts covered there. Code for the Supabase v1 implementation can be found under the v1 branch in GitHub.
-
User Authentication in Next.js with Supabase
All of the code in this article is available for reference in GitHub
rfcs
-
Easy React data fetching with the new `use()` hook
React.use() is still an unstable API. For more information check out the support for promises React RFC . At the time of writing this, you can only test this API in Next.js 13.
-
Authentication in Next.js with Supabase and Next 13
You see, root-level await is not supported in client-side components, and so we can't "suspend" our Home page until the session data is available like we do with Profile. React team is working on an RFC and a new use hook that will allow us to conditionally wait for data to load, but it's not quite ready yet. Its use (pardon the pun) is also not recommended by Next itself, as it may cause multiple re-renders in Client Components. Considering all that, we'll need to find an alternative way.
-
React use() hook explained in 2 minutes
I think it's better explained in the RFC: https://github.com/acdlite/rfcs/blob/first-class-promises/text/0000-first-class-support-for-promises.md
-
Next.js 13 - What are the new features?
Below is an example taken from here showing how to fetch data with async/await in Server Components.
-
What's New in Next.js 13
Being able to utilize async/await in Server Components is great and is part of React's RFC to add first-class support for Promises. It allows us to do what we just did in app/dashboard/page.tsx:
-
React Just Got Even More Awesome
More info here
- React RFC: First Class Support for Promises
What are some alternatives?
gotrue - An SWT based API for managing users and issuing SWT tokens.
tailwindcss-forms - A plugin that provides a basic reset for form styles that makes form elements easy to override with utilities.
auth-ui - Pre-built Auth UI for React
next-the-13th - Next.js 13 showcase
ui - Supabase UI Library
auth-helpers - A collection of framework specific Auth utilities for working with Supabase.
supabase-js - An isomorphic Javascript client for Supabase. Query your Supabase database, subscribe to realtime events, upload and download files, browse typescript examples, invoke postgres functions via rpc, invoke supabase edge functions, query pgvector.
Yup - Dead simple Object schema validation
formik - Build forms in React, without the tears 😠[Moved to: https://github.com/formium/formik]
realtime - Broadcast, Presence, and Postgres Changes via WebSockets