github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #8500] docs(dodopayments): docs still use deprecated authClient.dodopayments.checkout() #19738

New Issue
Closed
opened 2026-04-15 19:04:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 19:04:07 -05:00
Owner
Copy Link

Originally created by @Mnigos on GitHub (Mar 8, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/8500

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Open the Better Auth Dodo Payments docs:
  2. Go to the "Usage" section / "Creating a Checkout Session".
  3. The example still uses:
authClient.dodopayments.checkout(...)
  1. Compare that with:
    Dodo adapter docs: https://docs.dodopayments.com/developer-resources/better-auth-adaptor
    current package README / installed API
  2. Those sources recommend:
authClient.dodopayments.checkoutSession(...)

Current vs. Expected behavior

Current:
Better Auth canary docs still show authClient.dodopayments.checkout(...) as the primary checkout example.
Dodo docs and the installed package recommend authClient.dodopayments.checkoutSession(...) for new integrations.
This makes it unclear which client API should be used.

Expected:
Better Auth docs should consistently use authClient.dodopayments.checkoutSession(...) as the primary example.
If checkout(...) is kept for backward compatibility, it should be clearly labeled as deprecated / legacy everywhere.
Better Auth main docs, canary docs, and Dodo adapter docs should match.

What version of Better Auth are you using?

1.4.18

System info

{
  "system": {
    "platform": "darwin",
    "arch": "arm64",
    "version": "Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:40 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6041",
    "release": "24.6.0",
    "cpuCount": 14,
    "cpuModel": "Apple M4 Pro",
    "totalMemory": "48.00 GB",
    "freeMemory": "1.39 GB"
  },
  "node": {
    "version": "v22.15.0",
    "env": "development"
  },
  "packageManager": {
    "name": "bun",
    "version": "1.3.8"
  },
  "frameworks": null,
  "databases": null,
  "betterAuth": {
    "version": "Unknown",
    "config": null
  }
}

Which area(s) are affected? (Select all that apply)

Documentation

Auth config (if applicable)

import { betterAuth } from "better-auth";
import {
  checkout,
  dodopayments,
  portal,
  webhooks,
} from "@dodopayments/better-auth";

export const auth = betterAuth({
  plugins: [
    dodopayments({
      client: dodoPayments,
      createCustomerOnSignUp: true,
      use: [
        checkout({
          products: [
            { productId: "pdt_monthly", slug: "plus-monthly" },
            { productId: "pdt_annual", slug: "plus-annual" },
          ],
          successUrl: "/success",
          authenticatedUsersOnly: true,
        }),
        portal(),
        webhooks({
          webhookKey: process.env.DODO_PAYMENTS_WEBHOOK_SECRET!,
        }),
      ],
    }),
  ],
});

Additional context

@dodopayments/better-auth 1.4.3
dodopayments 2.23.2

Originally created by @Mnigos on GitHub (Mar 8, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/8500 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Open the Better Auth Dodo Payments docs: - https://better-auth.com/docs/plugins/dodopayments 2. Go to the "Usage" section / "Creating a Checkout Session". 3. The example still uses: ```ts authClient.dodopayments.checkout(...) ``` 4. Compare that with: Dodo adapter docs: https://docs.dodopayments.com/developer-resources/better-auth-adaptor current package README / installed API 5. Those sources recommend: ```ts authClient.dodopayments.checkoutSession(...) ``` ### Current vs. Expected behavior Current: Better Auth canary docs still show authClient.dodopayments.checkout(...) as the primary checkout example. Dodo docs and the installed package recommend authClient.dodopayments.checkoutSession(...) for new integrations. This makes it unclear which client API should be used. Expected: Better Auth docs should consistently use authClient.dodopayments.checkoutSession(...) as the primary example. If checkout(...) is kept for backward compatibility, it should be clearly labeled as deprecated / legacy everywhere. Better Auth main docs, canary docs, and Dodo adapter docs should match. ### What version of Better Auth are you using? 1.4.18 ### System info ```bash { "system": { "platform": "darwin", "arch": "arm64", "version": "Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:40 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6041", "release": "24.6.0", "cpuCount": 14, "cpuModel": "Apple M4 Pro", "totalMemory": "48.00 GB", "freeMemory": "1.39 GB" }, "node": { "version": "v22.15.0", "env": "development" }, "packageManager": { "name": "bun", "version": "1.3.8" }, "frameworks": null, "databases": null, "betterAuth": { "version": "Unknown", "config": null } } ``` ### Which area(s) are affected? (Select all that apply) Documentation ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth"; import { checkout, dodopayments, portal, webhooks, } from "@dodopayments/better-auth"; export const auth = betterAuth({ plugins: [ dodopayments({ client: dodoPayments, createCustomerOnSignUp: true, use: [ checkout({ products: [ { productId: "pdt_monthly", slug: "plus-monthly" }, { productId: "pdt_annual", slug: "plus-annual" }, ], successUrl: "/success", authenticatedUsersOnly: true, }), portal(), webhooks({ webhookKey: process.env.DODO_PAYMENTS_WEBHOOK_SECRET!, }), ], }), ], }); ``` ### Additional context `@dodopayments/better-auth` 1.4.3 `dodopayments` 2.23.2
GiteaMirror added the locked label 2026-04-15 19:04:07 -05:00
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 Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#19738
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?