Releases: nuxt-modules/supabase
v2.0.0
π Features
β οΈ Breaking changes
This release introduces support for Supabase JWT signing keys, bringing enhanced security and performance improvements.
π View Migration Guide to learn more about how to take advantage of JWT signing keys with Supabase.
Full Changelog: v1.6.2...v2.0.0
v1.6.2
π Bug Fixes
- fix(cookies): guard writes when response headers already in #525
β€οΈ New Contributors
- @nicokempe made their first contribution in #525
- @Shooteger made their first contribution in #523
Full Changelog: v1.6.1...v1.6.2
v1.6.1
π Bug Fixes
- types: use "unjs/pathe" to make the exported type use relative path by @Chrissi2812 in #516
- demo: database types (8da11e6)
- demo: link module (25cae97)
- playground: database types (58549ab)
New Contributors
- @Chrissi2812 made their first contribution in #516
Full Changelog: v1.6.0...v1.6.1
v1.6.0
Nuxt Supabase module is now compatible with Nuxt v4.
Please read the uprade guide to learn how to upgrade to the latest Nuxt version.
Full Changelog: v1.5.3...v1.6.0
v1.5.3
v1.5.2
v1.5.1
1.5.1 (2025-05-13)
π New Documentation
First Nuxt module documentation built with Docus v2 powered by Nuxt UI Pro (coming soon π)
π Bug Fixes
v1.5.0
1.5.0 (2025-03-04)
Bug Fixes
This release addresses multiple inconsistencies with cookie handling x customization that might fix several issues:
- Setting persistSession: false still persists auth session (#390)
- The module doesn't recognize supabase.clientOptions.auth.flowType key (#449)
- Detecting session in URL is not working when sending "Password recovery" email manually from Supabase dashboard (#397)
- Static Hosting: Client side only rendering gives error when signing in with email - pw (#138)
Features
- Added
useSsrCookies
option (default:true
) β Resolves #186
This new option controls whether the module uses cookies to share session info between server and client. You must enable this option if you need to access session or user info from the server. It will use the SSR client from the @supabase/ssr library.
When disabled, the module will use the default Supabase client from the @supabase/supabase-js library which stores session info in local storage. This is useful in certain cases, such as statically generated sites or mobile apps where cookies might not be available.
-
Renamed
cookieName
βcookiePrefix
β More accurate naming. -
Renamed
cookieRedirect
βsaveRedirectToCookie
β More accurate naming. -
New
useSupabaseCookieRedirect
composable β Simplifies handling redirect cookies without hardcoded names -
Docs updated:
useSsrCookies
β https://supabase.nuxtjs.org/get-started#usessrcookiescookiePrefix
β https://supabase.nuxtjs.org/get-started#cookieprefixasaveRedirectToCookie
β https://supabase.nuxtjs.org/get-started#redirectoptionsuseSupabaseCookieRedirect
β https://supabase.nuxtjs.org/usage/composables/usesupabasecookieredirect
Breaking Changes?
No. useSsrCookies
default value keep the old behaviour and deprecated options (cookieName
, cookieRedirect
) maintain backward compatibility.
Contributor π
A massive thanks to @Jordan-Ellis for this improvement.