docs
auth-helpers
Our great sponsors
docs | auth-helpers | |
---|---|---|
6 | 18 | |
14 | 880 | |
- | 2.3% | |
9.3 | 8.2 | |
2 days ago | 4 days ago | |
MDX | TypeScript | |
- | 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.
docs
-
Develop a Cryptocurrency Tracking WebApp with Instant Email Notifications
đź”— Courier Docs
-
How to Send Invoice and Add Payment Reminder in Next.js with Courier API
In this article, I will be integrating Courier to send emails for this project.
-
Build an Open Source NGL.link alternative with Next.js and the Courier API
Courier Documentation
- Docusaurus 2.0 – Meta's static site generator to build documentation sites
-
Common Courier Troubleshooting Solutions for Developers
With that said, we believe that in order to make software-to-human communication delightful, there needs to be an open line of communication with developers who have implemented Courier to handle their notification infrastructure. We want you to have as many support options as possible whether it’s self-serve through our docs and articles, or 1-1 with our engineers and support staff. We’re here to make your Courier experience as smooth as possible! If you’d prefer enterprise-level support, sign up for a demo request now!
-
How We Built Our Documentation on Docusaurus
There are a few more goals we have for our documentation. We have yet to utilize Docusaurus’s localization feature, so that’s in the works. We have also recently made our documentation open-source to welcome external contributors. This way, the user can take ownership of the updates they want and help themselves and others who would benefit from their contribution.
auth-helpers
-
Supabase Authentication Issue with Next.js 13.4 - !session vs !user
I have encountered a similar issue, but I haven't fully found a solution yet. Currently, I'm using the getSession function throughout my server components. Yesterday, I tried running a middleware to refresh the user's session, based on this example: https://github.com/supabase/auth-helpers/blob/main/examples/nextjs/middleware.tsx. This caught my attention because the comment mentioned that the middleware is necessary for any Server Component route using createServerComponentClient. Right now, I'm testing this approach, and so far, I haven't been logged out since yesterday. Do you have that in your application? The main difference between getSession and getUser in supabase is that getSession reads the cookies and is very fast (around 1-2 ms), while getUser makes a call to the supabase API with the access token to retrieve the user and I would assume they also verify the JWT on their end.
-
SvelteKit is awful for building PWAs
F.ex. Have a look how supabase-auth-helper-sveltekit works. This is the "SvelteKit way" to approach authentication. It also works perfectly with invalidate to reload or invalidate data that is connected to the current user session. As pointed out already, there is no reason you should not be able to access your JWT.
-
Supabase Beta May 2023
We have updated the Next.js Auth Helpers package to make it available across the client and server of the App Router. They also now implement server-side auth by default with PKCE - meaning the entire auth flow is now possible server-side.
-
Need some help with auth and nextjs13 (using app folder) that I just can't seem to wrap my head around something trivial
Example
- When to use which - page.ts VS page.server.ts
-
Help with basic Supabase setup on Next.js?
seems like known issue https://github.com/supabase/auth-helpers/issues/497
-
Use base gotrue api instead of auth helper
auth helper for sveltekit: https://github.com/supabase/auth-helpers/tree/main/packages/sveltekit
- How to add protected routes with server components?
- Issues with Sveltekit and Supabase Authentication
-
What do you think about handling protected routes and redirects in middleware?
I do think checking auth in a server component would likely be better for your use here. Supabase has a nice example here: https://github.com/supabase/auth-helpers/tree/main/examples/nextjs-server-components They have a simple case with Middleware, but you wouldn't need to do it that way. Can use "redirect(/login)" from the server component.
What are some alternatives?
notes - Collection of my byte sized notes on programming and other random topics.
sk-auth - Authentication library for use with SvelteKit featuring built-in OAuth providers and zero restriction customization!
remark-wiki-link - Parse and render wiki links.
sveltekit-prisma-example
lol
nextjs-supabase - Multi-tenant NextJS 13 + Supabase
mdx - Markdown for the component era
sveltekit-firebase9 - a simple todo app with sveltekit and firebase 9
CryptoTrack - Track your Cryptocurrencies and get instant email notification whenever they change
supabase-auth-helpers - A collection of framework specific Auth utilities for working with Supabase. [Moved to: https://github.com/supabase-community/auth-helpers]
react-native - A framework for building native applications using React
tailwindcss-forms - A plugin that provides a basic reset for form styles that makes form elements easy to override with utilities.