Jacob Comments - Answer Overflow

•Created by Jacob on 3/24/2025 in #help

Can't use @better-auth/cli when exporting a auth function

When running similiar code:

import { getMigrations } from "better-auth/db";
import { createAuth } from "./auth";

const auth = await createAuth(
  process.env.API_URL!,
  process.env.FRONT_END_URL!,
  process.env.AUTH_SECRET!,
  process.env.GOOGLE_CLIENT_ID!,
  process.env.GOOGLE_CLIENT_SECRET!,
  process.env.TURSO_CONNECTION_URL!,
  process.env.TURSO_AUTH_TOKEN!,
  process.env.RESEND_API_KEY!
);

const { runMigrations } = await getMigrations(auth.options);

await runMigrations(); //this will run the migrations for you

import { getMigrations } from "better-auth/db";
import { createAuth } from "./auth";

const auth = await createAuth(
  process.env.API_URL!,
  process.env.FRONT_END_URL!,
  process.env.AUTH_SECRET!,
  process.env.GOOGLE_CLIENT_ID!,
  process.env.GOOGLE_CLIENT_SECRET!,
  process.env.TURSO_CONNECTION_URL!,
  process.env.TURSO_AUTH_TOKEN!,
  process.env.RESEND_API_KEY!
);

const { runMigrations } = await getMigrations(auth.options);

await runMigrations(); //this will run the migrations for you

i end with this error:

 bun ./src/common/auth-migrate.ts
2025-03-30T05:10:41.783Z WARN [Better Auth]: Could not determine database type, defaulting to sqlite. Please provide a type in the database options to avoid this.
2025-03-30T05:10:41.783Z ERROR [Better Auth]: Only kysely adapter is supported for migrations. You can use `generate` command to generate the schema, if you're using a different adapter.

 bun ./src/common/auth-migrate.ts
2025-03-30T05:10:41.783Z WARN [Better Auth]: Could not determine database type, defaulting to sqlite. Please provide a type in the database options to avoid this.
2025-03-30T05:10:41.783Z ERROR [Better Auth]: Only kysely adapter is supported for migrations. You can use `generate` command to generate the schema, if you're using a different adapter.

this is my createAuth function:

export const createAuth = (
  /**Our API url */
  baseUrl: string,
  /**Where the fronted is hosted */
  frontEndUrl: string,
  /**Our auth secret to handle hashing */
  authSecret: string,
  googleClientId: string,
  googleClientSecret: string,
  /**Db connection URL */
  url: string,
  /** Db auth token */
  authToken: string,
  resendApiKey: string
) => {
  const db = createDb(url, authToken);

  return betterAuth({
    appName: "BuzzTrip",
    baseURL: baseUrl,
    basePath: "/auth",
    secret: authSecret,
    trustedOrigins: [frontEndUrl],
    database: drizzleAdapter(db, {
      provider: "sqlite", // or "mysql", "sqlite"`
      schema: {
        ...schemas,
        user: schemas.users,
      },
    }),
    // ... other options
  });
};

export type Auth = ReturnType<typeof createAuth>;

export const createAuth = (
  /**Our API url */
  baseUrl: string,
  /**Where the fronted is hosted */
  frontEndUrl: string,
  /**Our auth secret to handle hashing */
  authSecret: string,
  googleClientId: string,
  googleClientSecret: string,
  /**Db connection URL */
  url: string,
  /** Db auth token */
  authToken: string,
  resendApiKey: string
) => {
  const db = createDb(url, authToken);

  return betterAuth({
    appName: "BuzzTrip",
    baseURL: baseUrl,
    basePath: "/auth",
    secret: authSecret,
    trustedOrigins: [frontEndUrl],
    database: drizzleAdapter(db, {
      provider: "sqlite", // or "mysql", "sqlite"`
      schema: {
        ...schemas,
        user: schemas.users,
      },
    }),
    // ... other options
  });
};

export type Auth = ReturnType<typeof createAuth>;

8 replies

•Created by Jacob on 3/24/2025 in #help

Can't use @better-auth/cli when exporting a auth function

Oh cool, thank you for the example that’s very helpful

8 replies

•Created by Jacob on 3/24/2025 in #help

Can't use @better-auth/cli when exporting a auth function

Yeah okay, didn’t think of that, so have to call the function programmatically with the passed items and run the migration? What would something like this work? I am using bun

8 replies

•Created by chris_st on 3/21/2025 in #help

Server email OTP authentication

@chris_st I mean at the end of the day it's just a wrapper around an api, so you could just call the api. but on the server if you are just doing email/OTP you can do something like this: auth.api.signInMagicLink(); and auth.api.magicLinkVerify(); just pass the email through and then the token and you''l be set. seems like all methods that you can use on the client you can do on the server through auth.api hope that might help

5 replies

•Created by chris_st on 3/21/2025 in #help

Server email OTP authentication

Hey @chris_st, Any of the auth options needs to use server side for the service in general (email and password doesn't have to bed done server side), you form will run client side and than the funtion is run and calls the server in which is does the rest of the logic. Email OTP is supported you can do it a few ways: 1. Using the email verfication when using email & password: https://www.better-auth.com/docs/authentication/email-password#email-verification, this will make the user have to verfiy their email after signing in / up with thier email. 2. passwordless using Email OTP: https://www.better-auth.com/docs/plugins/email-otp or Magic Link: https://www.better-auth.com/docs/plugins/magic-link theses are plugin's however rather than builtin as an authentication option, this will send a code or magic link with token to the user just like verfiying their email, making it a form of passwordless authentication while when you use this you use authClient.signIn.magicLink() it will create the user they don't already exist. So if you are looking to just verify a users email when using email & password auth use the https://www.better-auth.com/docs/authentication/email-password#email-verification but if you are looking for passwordless auth you can use either Email OTP: https://www.better-auth.com/docs/plugins/email-otp or Magic Link: https://www.better-auth.com/docs/plugins/magic-link . Hope that helps

5 replies

•Created by Jacob on 12/5/2024 in #help

Default headers not setting in nextjs rpc requests

Sorry for the really late response, the issue ending up being that in dev we are using http for transit where the cookies needed a secure connection to send across so both front end and api had to be run using https to send cookies across in development

19 replies

•Created by Jacob on 1/8/2025 in #questions

Getting build errors after upgrading to nextjs 15 and react 19

How would I go about that?

4 replies

•Created by Jacob on 12/29/2024 in #questions

Error building nextjs application on vercel

The issue seemed to be the following: 1. instrumentationHook was not set in nextjs config:

  experimental: {
    instrumentationHook: true,
  },

  experimental: {
    instrumentationHook: true,
  },

2. Incorrect sentry version 3. missing configs

6 replies

•Created by Jacob on 12/29/2024 in #questions

Error building nextjs application on vercel

Yes but no

6 replies

•Created by Jacob on 12/5/2024 in #help

Default headers not setting in nextjs rpc requests

Assuming cookies are set very similar on web to mobile however not set to the api on web thinking cors or nextjs might be the issue as it doesn’t automatically attach headers to the request e.g cookies to external apis unless specified

19 replies

•Created by Jacob on 12/5/2024 in #help

Default headers not setting in nextjs rpc requests

The clerk cookies are set via the clerk nextjs sdk and read by the @hono/clerk provider that wraps the clerk back end node sdk. Here is the repo: https://github.com/jacobsamo/BuzzTrip/tree/improve-web

19 replies

•Created by Jacob on 12/5/2024 in #help

Default headers not setting in nextjs rpc requests

Hey @ambergristle my setup is split into 3 different part 1 the api (hono) the web app (nextjs) and 3 the mobile app (expo/react native) currently in my web app using clerk for auth it won’t send across the cookies to the hono api however my mobile app sends them across fine, feeling like it is a cors issue but not sure how to fix it or it could be something else internally

19 replies

•Created by Crian. on 11/23/2024 in #questions

T3 Turbo Add Another App

if your have any more questions feel free to reach out

4 replies

•Created by Crian. on 11/23/2024 in #questions

T3 Turbo Add Another App

depends on what your adding, if we are adding a new app e.g web app, mobile app, etc: 1. First we need to go to /apps 2. create a new folder with the name of the app or use a setup tool e.g nextjs: npx create-next-app@latest my-cool-app (this will create a new app with the name my-cool-app it will also prompt you for a name when creating) if your creating a new package: 1. go to /packages 2. create a new folder with the name of your package 3. run npm init -y to create a new package.json 4. change the "name" field in the package.json to the name of your package

{
  "name": "@acme/my-package",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

{
  "name": "@acme/my-package",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

then in here create your files to your hearts content

4 replies

•Created by Jacob on 11/23/2024 in #questions

Shadcn components not working in nextjs 15 / react 19

I get the error from quite a few other shadcn components too, e.g Sidebar, Tooltip, Dialog, Drawer, etc

5 replies

•Created by Jacob on 11/23/2024 in #questions

Shadcn components not working in nextjs 15 / react 19

the button component:

import * as React from "react"
import { Slot } from "@radix-ui/react-slot"
import { cva, type VariantProps } from "class-variance-authority"

import { cn } from "@/lib/utils"

const buttonVariants = cva(
  "inline-flex items-center justify-center gap-2 whitespace-nowrap rounded-md text-sm font-medium transition-colors focus-visible:outline-none focus-visible:ring-1 focus-visible:ring-ring disabled:pointer-events-none disabled:opacity-50 [&_svg]:pointer-events-none [&_svg]:size-4 [&_svg]:shrink-0",
  {
    variants: {
      variant: {
        default:
          "bg-primary text-primary-foreground shadow hover:bg-primary/90",
        destructive:
          "bg-destructive text-destructive-foreground shadow-sm hover:bg-destructive/90",
        outline:
          "border border-input bg-background shadow-sm hover:bg-accent hover:text-accent-foreground",
        secondary:
          "bg-secondary text-secondary-foreground shadow-sm hover:bg-secondary/80",
        ghost: "hover:bg-accent hover:text-accent-foreground",
        link: "text-primary underline-offset-4 hover:underline",
      },
      size: {
        default: "h-9 px-4 py-2",
        sm: "h-8 rounded-md px-3 text-xs",
        lg: "h-10 rounded-md px-8",
        icon: "h-9 w-9",
      },
    },
    defaultVariants: {
      variant: "default",
      size: "default",
    },
  }
)

export interface ButtonProps
  extends React.ButtonHTMLAttributes<HTMLButtonElement>,
    VariantProps<typeof buttonVariants> {
  asChild?: boolean
}

const Button = React.forwardRef<HTMLButtonElement, ButtonProps>(
  ({ className, variant, size, asChild = false, ...props }, ref) => {
    const Comp = asChild ? Slot : "button"
    return (
      <Comp
        className={cn(buttonVariants({ variant, size, className }))}
        ref={ref}
        {...props}
      />
    )
  }
)
Button.displayName = "Button"

export { Button, buttonVariants }

import * as React from "react"
import { Slot } from "@radix-ui/react-slot"
import { cva, type VariantProps } from "class-variance-authority"

import { cn } from "@/lib/utils"

const buttonVariants = cva(
  "inline-flex items-center justify-center gap-2 whitespace-nowrap rounded-md text-sm font-medium transition-colors focus-visible:outline-none focus-visible:ring-1 focus-visible:ring-ring disabled:pointer-events-none disabled:opacity-50 [&_svg]:pointer-events-none [&_svg]:size-4 [&_svg]:shrink-0",
  {
    variants: {
      variant: {
        default:
          "bg-primary text-primary-foreground shadow hover:bg-primary/90",
        destructive:
          "bg-destructive text-destructive-foreground shadow-sm hover:bg-destructive/90",
        outline:
          "border border-input bg-background shadow-sm hover:bg-accent hover:text-accent-foreground",
        secondary:
          "bg-secondary text-secondary-foreground shadow-sm hover:bg-secondary/80",
        ghost: "hover:bg-accent hover:text-accent-foreground",
        link: "text-primary underline-offset-4 hover:underline",
      },
      size: {
        default: "h-9 px-4 py-2",
        sm: "h-8 rounded-md px-3 text-xs",
        lg: "h-10 rounded-md px-8",
        icon: "h-9 w-9",
      },
    },
    defaultVariants: {
      variant: "default",
      size: "default",
    },
  }
)

export interface ButtonProps
  extends React.ButtonHTMLAttributes<HTMLButtonElement>,
    VariantProps<typeof buttonVariants> {
  asChild?: boolean
}

const Button = React.forwardRef<HTMLButtonElement, ButtonProps>(
  ({ className, variant, size, asChild = false, ...props }, ref) => {
    const Comp = asChild ? Slot : "button"
    return (
      <Comp
        className={cn(buttonVariants({ variant, size, className }))}
        ref={ref}
        {...props}
      />
    )
  }
)
Button.displayName = "Button"

export { Button, buttonVariants }

the repo: https://github.com/jacobsamo/BuzzTrip/tree/improve-web

5 replies

•Created by Mugetsu on 9/3/2024 in #questions

Use Zod schema after parse & transform as a new schema

Note: When using the .extend method even if you remove the field on the clientSchema it will still be there on the serverSchema

7 replies