First Release

[BracketJohn]

What do we still want to do before this library get's an alpha release?

• general
  • create a logo
  • test whether the following works, if it doesn't work potentially support it:
    • api
    • client api
    • middleware server
    • middleware client
    • server side access of auth data
    • optional: auth wrapper component -> out of scope
  • expand docs
    • client api
    • rest api
• composable
  • resolve remaining todos
  • move the composable into the module
  • optional: type _fetch better to get better typing for all methods
• next-auth backend proxy
  • resolve remaining todos
  • remove all console logs
  • cleanup proxy
• polishing & config
  • rename to @sidebase/nuxt-auth
  • pass through config
    • pass nextAuth config through nuxt.config to module to api endpoint, support complex provider objects
    • see Complex runtimeConfig values become {} inside the app  nuxt/nuxt#15237 by @danielroe
    • NEXTAUTH_SECRET support
    • optional: NEXTAUTH_URL support
    • optional: all config
  • remove test oauth credentials + delete oauth app
  • deploy a test-web-app at https://nuxt-user-example.sidebase.io/, @zoey-kaiser
• publishing
  • test publish alpha
  • package + publish
  • test it out in vanilla nuxt3 app
    • does it work?
    • does typing work?
  • do a beta testing release & collect feedback
  • do the first full release

[BracketJohn]

cc @zoey-kaiser

[BracketJohn]

publish a test-web-app with it, similar to https://next-auth-example.vercel.app/

this is in progress here: https://nuxt-user-example.sidebase.io/

repo (already public to host with GH pages): https://github.com/sidebase/nuxt-user-example

[BracketJohn]

pass nextAuth config through nuxt.config to module to api endpoint, support complex provider objects

@danielroe this is my concrete use-case I want the user to be able to pass complex config down through the nuxt.config:

import { defineNuxtConfig } from 'nuxt/config'
import GithubProvider from 'next-auth/providers/github'
import MyModule from '..'

export default defineNuxtConfig({
  modules: [
    MyModule
  ],
  user: {
    isEnabled: true,
    nextAuth: {
      providers: [GithubProvider.default({
        clientId: '123123',
        clientSecret: 'jklasdjklasdjklasdjkl213123123'
      })]
    }
  }
})

here, GithubProvider.default becomes a nested object with functions, that does not pass through the de-/serialization step we discussed here nuxt/nuxt#15237.

Any ideas on how to handle this best, ideally so that the user does not have to create their own files to make auth work?

---

If there's no good way to do it from the nuxt.config, I've considered an approach where the user has to create their auth endpoint themselves, similar to how they do it in the nextAuth.js docs, see here:

// `/server/api/auth.ts`
import NuxtAuth from "@sidebase/nuxt-user"

export default NuxtAuth({
  ...
})

[danielroe]

I would recommend something more like this:

export default defineNuxtConfig({
  modules: [
    MyModule
  ],
  user: {
    isEnabled: true,
    nextAuth: {
      providers: {
        // also acceptable would be an alias, e.g. `~/providers/github` to refer to user's own project dir
        'nuxt-auth/providers/github': {
          clientId: '123123',
          clientSecret: 'jklasdjklasdjklasdjkl213123123'
        }
      }
    }
  }
})

This keeps runtime + config code separate.

[BracketJohn]

And then the module does a dynamic import of github at runtime:

import GitHubProvider from "next-auth/providers/github";

?

[danielroe]

I tend to use the word module to refer to build time only code. In the runtime template you are generating you can generate the correct import. It doesn't need to be a dynamic import, though if it is appropriate you could also do that.

[BracketJohn]

Thanks! I generated nitro virtual imports to make this work now 👍

---

optional: type _fetch better to get better typing for all methods

Note to us: I improved this slightly, but there's still some way to go: TS should be able to auto-infer return types for _fetgch if done right

[BracketJohn]

we're done with the first release for some time now -> closing this issue