Add option to disable Telegram user fields for OIDC-only usage

[flxxxxddd]

Problem

When using better-auth-telegram with only the OIDC provider (oauth.telegram.org) and without the Telegram Login Widget or Mini App features, the plugin still injects user schema fields telegramId, telegramUsername, and telegramPhoneNumber. This forces additional columns in the user model and migrations even though they are unused for the OIDC flow. It increases DB surface area and complicates adoption for teams that only need OIDC.

Proposed Solution

Add a configuration flag (e.g., schema: { includeUserFields: false } or oidcOnly: true) that prevents the plugin from adding user schema fields (telegramId, telegramUsername, telegramPhoneNumber) when only OIDC is used. The account fields used for OAuth linking can remain if needed, but user-level Telegram fields should be optional and disabled by default in OIDC-only mode. Include docs and an example showing OIDC-only setup without extra user columns.

Alternatives Considered

No response

Additional Context

No response

[vcode-sh]

Fixed in v1.5.0. Your extra columns are now optional. You're welcome, your DBA is welcome.

The solution: loginWidget: false. That's it. When you set it, the plugin skips all Login Widget endpoints (/telegram/signin, /telegram/link, /telegram/unlink) AND — the bit you actually care about — omits telegramId, telegramUsername, and telegramPhoneNumber from the user table, plus telegramId and telegramUsername from the account table. Five columns, gone. OIDC-only setup, clean schema.

telegram({
  botToken: process.env.TELEGRAM_BOT_TOKEN!,
  botUsername: "your_bot",
  loginWidget: false,
  oidc: {
    enabled: true,
    clientSecret: process.env.TELEGRAM_OIDC_SECRET!,
  },
})

The logic: schema fields are only injected when widgetEnabled || miniAppEnabled. If you've disabled the widget and haven't enabled Mini Apps, you get undefined — no schema extension, no migrations, no existential dread about unused columns.

Edge case covered: if you have loginWidget: false but miniApp: { enabled: true }, the fields come back — Mini App flows need them. Makes sense, you asked for Mini App support, you get Mini App columns.

26 new tests covering schema derivation, endpoint registration, config response, rate limits, and backward compatibility. The "OIDC-only → schema is undefined" case is tested explicitly.

npm install better-auth-telegram@1.5.0