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

1.5.3 (2025-06-27)

Bug Fixes

• ci: pnpm version (1acc409)
• config: logo paths (891d3c8)
• deps: upgrade supabase-js (162e559)

v1.5.2

1.5.2 (2025-06-12)

Bug Fixes

• demo: login screen height (09f697b)
• demo: redirect github provider (be12884)
• demo: redirect url for github provider (1fd67f8)
• demo: remove toggle (e741537)
• demo: use head (65832ba)

v1.5.1

1.5.1 (2025-05-13)

📖 New Documentation

https://supabase.nuxtjs.org/

First Nuxt module documentation built with Docus v2 powered by Nuxt UI Pro (coming soon 👀)

🐛 Bug Fixes

• plugins: do not set states on client (#490) (6152a64)
• serverSupabaseClient: pass H3Event into useRuntimeConfig (#491) (548e21e)

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#usessrcookies
  • cookiePrefix → https://supabase.nuxtjs.org/get-started#cookieprefixa
  • saveRedirectToCookie→ https://supabase.nuxtjs.org/get-started#redirectoptions
  • useSupabaseCookieRedirect → 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.

v1.4.6

What's Changed

Bug Fixes

• serverSupabaseServiceRole: Pass H3Event into useRuntimeConfig (#450) (2de1c08)

Full changelog (2025-01-20)

Contributors 💚

@blackburn32

v1.4.5

What's Changed

Fix

• deps: Update supabase-js to fix #442 and #264

Full changelog (2024-12-18)

v1.4.4

What's Changed

Feature

• deps: Update supabase-js to fix realtime issue (#436)

Full changelog (2024-12-10)

Contributors 💚

@felixgabler