Can't generate migrations using D1 on Cloudflare Workers

There is no way to run migrations while using D1 with Kysely on Cloudflare for 2 reasons:

The DB is exposed only at runtime, aka we cannot use the
```
better-auth CLI
```
better-auth CLI
```
better-auth CLI
```
better-auth CLI
to detect the configuration since it's only looking for variables exported (when using D1 we construct the configuration with each request and we only have a function)
The usage of
```
getMigrations
```
getMigrations
```
getMigrations
```
getMigrations
is still undocumented and probably abandoned since It's returning generic errors from D1 such as
```
Error: D1_ERROR: not authorized: SQLITE_AUTH
```
Error: D1_ERROR: not authorized: SQLITE_AUTH
```
Error: D1_ERROR: not authorized: SQLITE_AUTH
```
Error: D1_ERROR: not authorized: SQLITE_AUTH

const { getMigrations } = await import("better-auth/db");
const { auth } = await import("@/lib/auth");

const GET_HANDLER = async () => {
  try {
    console.log(auth().options.database.db);
    const { toBeCreated, toBeAdded, compileMigrations } = await getMigrations(
      auth().options,
    );

    if (!toBeCreated.length && !toBeAdded.length) {
      return Response.json(
        { status: "success", message: "No schema changes detected" },
        { status: 200 },
      );
    }

    const schema = await compileMigrations();

    return Response.json(
      { status: "success", message: schema },
      { status: 200 },
    );
  } catch (err) {
    console.error(err);
    return new Response(null, { status: 500 });
  }
};

export { GET_HANDLER as GET };

const { getMigrations } = await import("better-auth/db");
const { auth } = await import("@/lib/auth");

const GET_HANDLER = async () => {
  try {
    console.log(auth().options.database.db);
    const { toBeCreated, toBeAdded, compileMigrations } = await getMigrations(
      auth().options,
    );

    if (!toBeCreated.length && !toBeAdded.length) {
      return Response.json(
        { status: "success", message: "No schema changes detected" },
        { status: 200 },
      );
    }

    const schema = await compileMigrations();

    return Response.json(
      { status: "success", message: schema },
      { status: 200 },
    );
  } catch (err) {
    console.error(err);
    return new Response(null, { status: 500 });
  }
};

export { GET_HANDLER as GET };

const { getMigrations } = await import("better-auth/db");
const { auth } = await import("@/lib/auth");

const GET_HANDLER = async () => {
  try {
    console.log(auth().options.database.db);
    const { toBeCreated, toBeAdded, compileMigrations } = await getMigrations(
      auth().options,
    );

    if (!toBeCreated.length && !toBeAdded.length) {
      return Response.json(
        { status: "success", message: "No schema changes detected" },
        { status: 200 },
      );
    }

    const schema = await compileMigrations();

    return Response.json(
      { status: "success", message: schema },
      { status: 200 },
    );
  } catch (err) {
    console.error(err);
    return new Response(null, { status: 500 });
  }
};

export { GET_HANDLER as GET };

const { getMigrations } = await import("better-auth/db");
const { auth } = await import("@/lib/auth");

const GET_HANDLER = async () => {
  try {
    console.log(auth().options.database.db);
    const { toBeCreated, toBeAdded, compileMigrations } = await getMigrations(
      auth().options,
    );

    if (!toBeCreated.length && !toBeAdded.length) {
      return Response.json(
        { status: "success", message: "No schema changes detected" },
        { status: 200 },
      );
    }

    const schema = await compileMigrations();

    return Response.json(
      { status: "success", message: schema },
      { status: 200 },
    );
  } catch (err) {
    console.error(err);
    return new Response(null, { status: 500 });
  }
};

export { GET_HANDLER as GET };

This is from within a Next.js app running with

Opennext

Opennext

Opennext

Opennext on Cloudflare Workers, everything else

better-auth

better-auth

related works like a charm, but if we can't make migration generation is useless, applying the migrations can be done with

wrangler

wrangler

against D1, but if we cannot generate the schema according to the current state of the DB we cannot add plugins efficiently by possible knowing what tables to alter and what to add or remove.

Any help would be much appreciated!

mihaaaiOP•3/30/25, 10:44 PM

The error happens just when trying to invoke the URL for the migration set within the app, returning a 500 and the error message on the server-side.
auth()auth() is using the getCloudflareContext()getCloudflareContext() function from opennext to get the runtime environment to reference D1 in Kysely config.

export const auth = () =>
  betterAuth({
    database: {
      db: new Kysely({
        dialect: new D1Dialect({
          database: getCloudflareContext().env.AUTH_DB,
        }),
      }),
      type: "sqlite",
    }
  }
)

export const auth = () =>
  betterAuth({
    database: {
      db: new Kysely({
        dialect: new D1Dialect({
          database: getCloudflareContext().env.AUTH_DB,
        }),
      }),
      type: "sqlite",
    }
  }
)

Ping•3/31/25, 6:34 AM

If you want to run migrations using CF d1 then I recommend having two auth instances, one is fake and for the purpose of better suth cli to detect and generate/migrate schemas, the other is real and for the purpose of your app.
Keep the fake auth instance in auth.ts, and just export auth as usual as how defining better auth would in most other integrations.

I recommend exporting your wuth config, then importing it across both auth instances to keep it consistant

�

🌠kkMihai ⚡•3/31/25, 9:49 AM

or just do this

Matt•4/1/25, 4:39 PM

I do exactly what Ping suggests - I have an auth.server.tsauth.server.ts in <projectRoot>/app/auth/ and then I have an

auth.ts

auth.ts

file in the project root.

Can't generate migrations using D1 on Cloudflare Workers

Similar Threads

Similar Threads

Similar Threads