github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-10-18 11:32:15 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

Importing User Additional Fields From Other File Failed!!! #210

New Issue
Closed
opened 2026-03-13 07:37:47 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 07:37:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @0xPratikPatil on GitHub (Nov 11, 2024).

Describe the bug
In my app, there are many user fields, so I thought of storing all the additional fields in a separate file to import them into the auth file, but I am unable to do that.

To Reproduce

import { additionalUserFields } from "./additional-fields";
import { betterAuth } from "better-auth";

export const auth = betterAuth({
  database: prismaAdapter(db, {
    provider: "mongodb",
  }),
  user: {
      additionalFields:additionalUserFields
  },
 });

 export const additionalUserFields = {
  timezone: {
    type: "string",
    required: false,
  },
  language: {
    type: "string",
    required: false,
  },
  urls: {
    type: "object",
    required: false,
  },
  pronouns: {
    type: "string",
    required: false,
  },
  bio: {
    type: "string",
    required: false,
  },
};

Error

(property) additionalFields?: {
    [key: string]: FieldAttribute<FieldType>;
} | undefined

Expected behavior
It must accept the imported additional fields with proper type safety

Originally created by @0xPratikPatil on GitHub (Nov 11, 2024). **Describe the bug** In my app, there are many user fields, so I thought of storing all the additional fields in a separate file to import them into the auth file, but I am unable to do that. **To Reproduce** ``` import { additionalUserFields } from "./additional-fields"; import { betterAuth } from "better-auth"; export const auth = betterAuth({ database: prismaAdapter(db, { provider: "mongodb", }), user: { additionalFields:additionalUserFields }, }); ``` ``` export const additionalUserFields = { timezone: { type: "string", required: false, }, language: { type: "string", required: false, }, urls: { type: "object", required: false, }, pronouns: { type: "string", required: false, }, bio: { type: "string", required: false, }, }; ``` **Error** ``` (property) additionalFields?: { [key: string]: FieldAttribute<FieldType>; } | undefined ``` **Expected behavior** It must accept the imported additional fields with proper type safety
GiteaMirror commented 2026-03-13 07:37:49 -05:00
Author
Owner
Copy Link
Copy Source

@0xPratikPatil commented on GitHub (Nov 11, 2024):

Right now, it works when I add any to additionalUserFields, but proper type safety is still needed. Also, add more documentation for additional user fields.

@0xPratikPatil commented on GitHub (Nov 11, 2024): Right now, it works when I add any to additionalUserFields, but proper type safety is still needed. Also, add more documentation for additional user fields.
GiteaMirror commented 2026-03-13 07:37:49 -05:00
Author
Owner
Copy Link
Copy Source

@0xPratikPatil commented on GitHub (Nov 11, 2024):

Also, please add JSON type in the additional fields and any other important field types.

@0xPratikPatil commented on GitHub (Nov 11, 2024): Also, please add JSON type in the additional fields and any other important field types.
GiteaMirror commented 2026-03-13 07:37:49 -05:00
Author
Owner
Copy Link
Copy Source

@Bekacru commented on GitHub (Nov 11, 2024):

This is cause the type has a mismatch since ts for example would infer type on the field type as just a string but Better Auth expects a "string" | "number" ... literal values instead. One way you could easily fix this is by casting the object with as const.

For example:

 export const additionalUserFields = {
  timezone: {
    type: "string",
    required: false,
  },
  language: {
    type: "string",
    required: false,
  },
  urls: {
    type: "object",
    required: false,
  },
  pronouns: {
    type: "string",
    required: false,
  },
  bio: {
    type: "string",
    required: false,
  },
} as const;
@Bekacru commented on GitHub (Nov 11, 2024): This is cause the type has a mismatch since ts for example would infer `type` on the field type as just a string but Better Auth expects a "string" | "number" ... literal values instead. One way you could easily fix this is by casting the object with `as const`. For example: ```ts export const additionalUserFields = { timezone: { type: "string", required: false, }, language: { type: "string", required: false, }, urls: { type: "object", required: false, }, pronouns: { type: "string", required: false, }, bio: { type: "string", required: false, }, } as const; ```
GiteaMirror commented 2026-03-13 07:37:49 -05:00
Author
Owner
Copy Link
Copy Source

@0xPratikPatil commented on GitHub (Nov 11, 2024):

Yes, it worked. Thank you. You can close the issue.

@0xPratikPatil commented on GitHub (Nov 11, 2024): Yes, it worked. Thank you. You can close the issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#210