basic white guy Posts - Answer Overflow

basic white guy

Explore posts from servers

•Created by basic white guy on 3/4/2025 in #help

Incorrect type inference with additionalFields inside a monorepo

I am using BetterAuth inside the packages directory of my Turborepo.

export type Session = typeof auth.$Infer.Session;
export type User = (typeof auth.$Infer.Session)["user"];

export type Session = typeof auth.$Infer.Session;
export type User = (typeof auth.$Infer.Session)["user"];

According to the BetterAuth documentation, the Session type should be inferred correctly using typeof auth.$Infer.Session. However, when I hover over User, I get the following inferred type:

type User = {
    id: string;
    email: string;
    emailVerified: boolean;
    name: string;
    createdAt: Date;
    updatedAt: Date;
    image?: string | null | undefined | undefined;
}

type User = {
    id: string;
    email: string;
    emailVerified: boolean;
    name: string;
    createdAt: Date;
    updatedAt: Date;
    image?: string | null | undefined | undefined;
}

This does not include the additional fields I defined in user.additionalFields. Am I missing a step to ensure the custom fields are included in the inferred type?

4 replies

BABetter Auth

•Created by basic white guy on 2/12/2025 in #help

extending google social login scope not working

As stated above I am trying to extend the google scope

  socialProviders: {
    // https://www.better-auth.com/docs/authentication/google
    google: {
      clientId: process.env.GOOGLE_CLIENT_ID!,
      clientSecret: process.env.GOOGLE_CLIENT_SECRET!,
      scope: [
        "https://www.googleapis.com/auth/user.birthday.read",
        "https://www.googleapis.com/auth/user.gender.read",
        "https://www.googleapis.com/auth/user.phonenumbers.read",
      ],
      mapProfileToUser: async (profile) => {
        console.log("🚀 ~ mapProfileToUser: ~ profile:", profile);

        return {
          firstName: profile.given_name,
          lastName: profile.family_name,
          name: `${profile.given_name} ${profile.family_name}`,
          image: profile.picture,
          email: profile.email,
          emailVerified: true,
        };
      },
    },

  socialProviders: {
    // https://www.better-auth.com/docs/authentication/google
    google: {
      clientId: process.env.GOOGLE_CLIENT_ID!,
      clientSecret: process.env.GOOGLE_CLIENT_SECRET!,
      scope: [
        "https://www.googleapis.com/auth/user.birthday.read",
        "https://www.googleapis.com/auth/user.gender.read",
        "https://www.googleapis.com/auth/user.phonenumbers.read",
      ],
      mapProfileToUser: async (profile) => {
        console.log("🚀 ~ mapProfileToUser: ~ profile:", profile);

        return {
          firstName: profile.given_name,
          lastName: profile.family_name,
          name: `${profile.given_name} ${profile.family_name}`,
          image: profile.picture,
          email: profile.email,
          emailVerified: true,
        };
      },
    },

when logging the mapProfileToUser which comes back with the user information it doesn't display of the information that I made requried

1 replies

BABetter Auth

•Created by basic white guy on 2/11/2025 in #help

callbackOnVerification receives user as null

I'm running into an issue where callbackOnVerification is getting user as null after phone verification.
user in callbackOnVerification is coming back as null, making it impossible to update the database with the verified phone number.
Handling OTP Verification:

const handleVerifyOTP = async () => {
  await authClient.phoneNumber.verify(
    {
      phoneNumber: form.getValues("phoneNumber"),
      code: pin,
      // disableSession: true,  // TODO: make sure if needed 
    },
    {
      onError: (error) => {
        toast({
          title: "OTP Verification Failed",
          description: error.error.message,
          variant: "destructive",
        });
      },
      onSuccess: () => {
        toast({
          title: "OTP Verified",
          description: "Your OTP has been verified successfully",
          variant: "default",
        });
        navigate({
          to: "/dashboard",
          replace: true,
        });
      },
    }
  );
};

const handleVerifyOTP = async () => {
  await authClient.phoneNumber.verify(
    {
      phoneNumber: form.getValues("phoneNumber"),
      code: pin,
      // disableSession: true,  // TODO: make sure if needed 
    },
    {
      onError: (error) => {
        toast({
          title: "OTP Verification Failed",
          description: error.error.message,
          variant: "destructive",
        });
      },
      onSuccess: () => {
        toast({
          title: "OTP Verified",
          description: "Your OTP has been verified successfully",
          variant: "default",
        });
        navigate({
          to: "/dashboard",
          replace: true,
        });
      },
    }
  );
};

Auth configuration (callbackOnVerification issue):

callbackOnVerification: async ({ phoneNumber, user }) => {
  // user is null here
  console.log("~ data, request:", phoneNumber, user);

  await db
    .update(UserTable)
    .set({ phoneNumberVerified: true, phoneNumber })
    .where(eq(UserTable.id, user?.id ?? ""));
};

callbackOnVerification: async ({ phoneNumber, user }) => {
  // user is null here
  console.log("~ data, request:", phoneNumber, user);

  await db
    .update(UserTable)
    .set({ phoneNumberVerified: true, phoneNumber })
    .where(eq(UserTable.id, user?.id ?? ""));
};

Question: Is there a way to ensure the user object is always available in callbackOnVerification? Could this be related to disableSession: true in handleVerifyOTP, or is there another way to retrieve the user at this stage?

2 replies

BABetter Auth

•Created by basic white guy on 2/3/2025 in #help

Additional Fields default value not being applied (drizzle)

In my auth.ts I am trying to add a few fields to the user table

  user: {
    additionalFields: {
      firstName: {
        type: "string",
        required: true,
        fieldName: "first_name",
      },
      lastName: {
        type: "string",
        required: true,
        fieldName: "last_name",
      },
      dob: {
        type: "date",
        required: true,
        fieldName: "dob",
      },
      rollingNetDepositLimit: {
        type: "number",
        required: true,
        fieldName: "rolling_net_deposit_limit",
        defaultValue: 160000,
      },
      isLocked: {
        type: "boolean",
        required: true,
        fieldName: "is_locked",
        defaultValue: false,
      },
    },
  },

  user: {
    additionalFields: {
      firstName: {
        type: "string",
        required: true,
        fieldName: "first_name",
      },
      lastName: {
        type: "string",
        required: true,
        fieldName: "last_name",
      },
      dob: {
        type: "date",
        required: true,
        fieldName: "dob",
      },
      rollingNetDepositLimit: {
        type: "number",
        required: true,
        fieldName: "rolling_net_deposit_limit",
        defaultValue: 160000,
      },
      isLocked: {
        type: "boolean",
        required: true,
        fieldName: "is_locked",
        defaultValue: false,
      },
    },
  },

I have this command in my package.json to

"auth:generate": "pnpm dlx @better-auth/cli@latest generate --y --output ./lib/server/schema/auth.schema.ts && prettier --write ./lib/server/schema/auth.schema.ts",

"auth:generate": "pnpm dlx @better-auth/cli@latest generate --y --output ./lib/server/schema/auth.schema.ts && prettier --write ./lib/server/schema/auth.schema.ts",

that will generate to auth.schema.ts but when the user table is being generated it displays this

export const user = pgTable("user", {
  id: text("id").primaryKey(),
  name: text("name").notNull(),
  email: text("email").notNull().unique(),
  emailVerified: boolean("email_verified").notNull(),
  image: text("image"),
  createdAt: timestamp("created_at").notNull(),
  updatedAt: timestamp("updated_at").notNull(),
  phoneNumber: text("phone_number").unique(),
  phoneNumberVerified: boolean("phone_number_verified"),
  firstName: text("first_name").notNull(),
  lastName: text("last_name").notNull(),
  dob: timestamp("dob").notNull(),
  rollingNetDepositLimit: integer("rolling_net_deposit_limit").notNull(),
  isLocked: boolean("is_locked").notNull(),
});

export const user = pgTable("user", {
  id: text("id").primaryKey(),
  name: text("name").notNull(),
  email: text("email").notNull().unique(),
  emailVerified: boolean("email_verified").notNull(),
  image: text("image"),
  createdAt: timestamp("created_at").notNull(),
  updatedAt: timestamp("updated_at").notNull(),
  phoneNumber: text("phone_number").unique(),
  phoneNumberVerified: boolean("phone_number_verified"),
  firstName: text("first_name").notNull(),
  lastName: text("last_name").notNull(),
  dob: timestamp("dob").notNull(),
  rollingNetDepositLimit: integer("rolling_net_deposit_limit").notNull(),
  isLocked: boolean("is_locked").notNull(),
});

it makes the fields required but the default values are not being applied

7 replies

TTCTheo's Typesafe Cult

•Created by basic white guy on 2/29/2024 in #questions

Incredibly Slow ESLint in t3-turbo Monorepo

I am using T3 Turbo and as the monorepo has grown (2 mid sized Next apps and a couple of packages), I've noticed that ESLint is running exceptionally slow on save, taking between 3-7 seconds. I'm using a M1 Mac. Interestingly, Saving inside the packages folder, for example, is relatively fast; it's only the Next apps that are experiencing the slowdown. Has anyone else experienced this?

2 replies

Gaming

Programming