To use the new version:

npm i -D @sidebase/[email protected]

See the docs here: https://sidebase.io/nuxt-auth/getting-started

What's Changed

This release is a bigger one and contains some breaking things, which is why we go from 0.2 to 0.3. If you were already using 0.3.0-alpha.X you're fine and none of the below breaking changes apply to you.

In comparison to 0.2.x this release:

• feat: delegates auth- and session-lifecycle management to a plugin
• feat!: makes useSession sync based on this change: no more await in your setup code
• feat: adds lastRefreshedAt to the session properties to allow you to act based on this time
• feat!: adds a auth middleware, use it:
  • globally via the nuxt.config.ts: https://github.com/sidebase/nuxt-auth#global-middleware
  • locally via definePageMeta: https://github.com/sidebase/nuxt-auth#local-middleware
• feat!: getCsrfToken returns the token string directly, instead of an object that contains the token
• refactors the internal structure a bit: add utils/ folders, clean up some typing and comments

Breaking changes

1. feat!: makes useSession sync

useSession is now synchronous. The initial session is fetched via a plugin that is loaded on app-startup. In your app replace:

// 1. old way to get data and status without forcing auth
const { data, status } = await useSession({ required: false })

// 2. old way to force auth
await useSession()

with:

// 1. new way to get data and status without forcing auth
const { data, status } = useSession()

// 2. new way to force auth: there's 2
// - recommended: use middlewares, read on in breaking change number (2) below or in docs https://github.com/sidebase/nuxt-auth#middleware
// - possible to support old-style manual checks:
const { getSession } = useSession()
await getSession()

and you're good to go. Note that useSession will also not directly force a login anymore. This is instead done via the new authentication middleware, see the related change below at number (2).

2. feat!: adds a auth middleware

This is a new approach to page protection that works either globally for the whole app or locally for certain pages. Check out the docs on this here: https://github.com/sidebase/nuxt-auth#middleware

If you want to keep using the 0.2.x approach of writing protection middlewares yourself, you can do this as follows:

const { getSession } = useSession()

// This will trigger a redirect if not logged in, just as `await useSession()` used to do. Also supports same additional options like `callbackUrl`
await getSession({ required: true })  

3. feat!: getCsrfToken returns the token string directly, instead of an object that contains the token

The return of getCsrfToken changed:

// old
console.log(await getCsrfToken())
// outputs: { token: 'asdfjklasdhjklasdhjlasdjlasdjkljklasd' }


// new
console.log(await getCsrfToken())
// outputs: 'asdfjklasdhjklasdhjlasdjlasdjkljklasd'

Commites

• Make use session sync, use a plugin based approach for session fetching by @BracketJohn in #69

• fix: don't set loading to true on use getSession by @JoaoPedroAS51 in #75

• fix: nuxt instance unavailable by @BracketJohn in #78

• feat: add trustHost option and fallback to host if not in production by @JoaoPedroAS51 in #76

• docs: switch to docus, rework all docs, add more docs by @BracketJohn in #90

• docs: Fixed redirect link in docs by @zoey-kaiser in #92

• fix(middleware): redirect to signIn using location.replace by @JoaoPedroAS51 in #87

• Updated images in README.md by @zoey-kaiser in #93

• fix: use exact nextauth version to avoid breaking change by @BracketJohn in #94

• release: 0.3.0-alpha.1 by @BracketJohn in #73

• release: 0.3.0-alpha.2 by @BracketJohn in #79

• release: 0.3.0-alpha.3 by @BracketJohn in #80

• release: 0.3.0 by @BracketJohn in #95

New Contributors

• @JoaoPedroAS51 made their first contribution in #75

Full Changelog: 0.2.1...0.3.0