Releases: nuxt-modules/supabase
v1.2.1
What's Changed
Improvements
Performance improvements by @vinceglb in #352
Chore
Move to eslint v9 using @nuxt/eslint package
💚 Thanks for the help from:
v1.2.0
What's Changed
Minor version since we have a new composable 🎉
useSupabaseSession and serverSupabaseSession are now available to fetch your session client and server side (#338) (07eb081 & 9dee37e)
Thanks @joeychilson for this feature 🙏
v1.1.7
What's Changed
Features
💚 Thanks for the help from
v1.1.6
What's Changed
Bug Fixes
Features
💚 Thanks for the help from
v1.1.5
What's Changed
Bug Fixes
- server: fetch user from session (7a3b73c)
Improvements
- app: use module-builder stub mode for more accurate types #315
Docs
💚 Thanks for the help from
v1.1.4
v1.1.3
v1.1.2
What's Changed
Breaking change is related to #244 and was first adressed in the v1.1.0
but patch has been necessary to fix the version.
On the confirm page, configured in redirect.callback
option (default to /confirm
), ensure to set the immediate
option in the watch.
Check out the doc: http://supabase.nuxtjs.org/authentication#confirm-page-confirm
Check out the demo code: https://github.com/nuxt-modules/supabase/blob/main/demo/pages/confirm.vue
Bug Fixes
- module: priority of redirect options made by defu (#256) (c4e30bf)
- plugin: retrieve user for client only page (#244) (4a35428)
- useSupabaseUser: add explicit user type (#254) (60d8551)
Full Changelog: v1.0.2...v1.1.0
💚 Thanks for the help from 💚
@52cs
@Aietes
@AlbertBrand
@kiri10ten
@xMorthi
v1.0.2
v1.0.1
I am happy to announce the release of version 1.0.0
of this module. While the module has been production-ready for quite some time, I never had the opportunity to create the first major version until now. Given that this version incorporates significant changes, I believe it is the perfect moment to establish this initial major release.
What's changed
-
Supabase introduced a new authentication flow (PKCE) a few months ago, which is now the default behavior of the module. However, you can still revert to the old (and less secure) authentication method through the module configuration. To help you seamlessly integrate this new flow, a dedicated section has been added to the documentation. (#219)
-
Building upon the previous point, we have implemented substantial changes to the session management, involving alterations to how Supabase clients are instantiated and how sessions are synchronized between the server and client-side. Consequently, these changes result in some breaking changes, which are listed below.
-
A brand new documentation has been built entirely using Nuxt Studio. Feel free to create PRs to suggest fixes or add any necessary changes to further enhance the documentation. (#210 / #221) => https://supabase.nuxtjs.org
Here's documentation that can help you understand the PKCE authentication flow:
- https://supabase.com/blog/supabase-auth-sso-pkce#server-side-and-mobile-auth
- https://supabase.com/docs/guides/resources/glossary#pkce
useSupabaseAuthClient
has been removed in favor ofuseSupabaseClient
in all casesserverSupabaseClient
is now returning a promise (should be called withawait
in anasync
method)redirect
option is enable by default, follow this guide to update your appclient
option becomesclientOptions
with new default value (including the PKCE flow)cookies
options is split incookieName
andcookieOptions
, default values have not changed
Here si the commit done for updating the demo with the last version: 10e0586
A huge thanks to @Aietes for initialising all those changes and help me built it 💚