BA
Better Auth•6mo ago
mihaaai

Can't use Cloudflare D1 database with Hono backend on Cloudflare Workers

Due to the fact that the env context is only exposed to incoming requests, It can't seem to be possible to create a config for better-auth on Hono using the D1 Database from Cloudflare Workers. This example of D1 with better-auth is for the OpenNext new implementation for Workers, I'm wondering if there's a way to set it up also on Hono. I've been able to make it work from SolidStart with a similar configuration but I'm stuck on Hono, and I'd prefer to have the server backend of better-auth on a separate Hono Worker without relying on CF Functions from the full-stack app. 
import { betterAuth } from "better-auth";
import { anonymous } from "better-auth/plugins";
import { Kysely } from "kysely";
import { D1Dialect } from "kysely-d1";
// Can't get a reference of D1 from here since it's outside the incoming request scope

export const auth = betterAuth({
  database: {
    db: new Kysely({
      dialect: new D1Dialect({
        database: process.env.DB as unknown as D1Database, // this results in database: undefined
      }),
    }),
    type: "sqlite",
  },
  emailAndPassword: {
    enabled: true,
  },
  plugins: [anonymous()],
});
import { betterAuth } from "better-auth";
import { anonymous } from "better-auth/plugins";
import { Kysely } from "kysely";
import { D1Dialect } from "kysely-d1";
// Can't get a reference of D1 from here since it's outside the incoming request scope

export const auth = betterAuth({
  database: {
    db: new Kysely({
      dialect: new D1Dialect({
        database: process.env.DB as unknown as D1Database, // this results in database: undefined
      }),
    }),
    type: "sqlite",
  },
  emailAndPassword: {
    enabled: true,
  },
  plugins: [anonymous()],
});
13 Replies
Unknown User
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
mihaaai
mihaaaiOP•6mo ago
Thanks for the tip, didn't see that method before, but it's still not reliable. After attaching the app.use(contextStorage()) in the main app index.ts file I still can't make it work 
import { betterAuth } from "better-auth";
import { anonymous } from "better-auth/plugins";
import { Kysely } from "kysely";
import { D1Dialect } from "kysely-d1";
import { getContext } from "hono/context-storage";

type Env = {
  Bindings: {
    DB: D1Database;
  };
};

export const auth = betterAuth({
  database: {
    db: new Kysely({
      dialect: new D1Dialect({
        database: getContext<Env>().env.DB,
      }),
    }),
    type: "sqlite",
  },
  emailAndPassword: {
    enabled: true,
  },
  plugins: [anonymous()],
});
import { betterAuth } from "better-auth";
import { anonymous } from "better-auth/plugins";
import { Kysely } from "kysely";
import { D1Dialect } from "kysely-d1";
import { getContext } from "hono/context-storage";

type Env = {
  Bindings: {
    DB: D1Database;
  };
};

export const auth = betterAuth({
  database: {
    db: new Kysely({
      dialect: new D1Dialect({
        database: getContext<Env>().env.DB,
      }),
    }),
    type: "sqlite",
  },
  emailAndPassword: {
    enabled: true,
  },
  plugins: [anonymous()],
});
With this in place and the dev server running, trying to run npx @better-auth/cli generate or npx @better-auth/cli migrate will still result in ERROR [#better-auth]: Couldn't read your auth config. Context is not available These commands are working from a SolidStart App that is bounded through Service Binding to the same worker in a much complex way, it's frustrating not being able to bind it directly in Hono because of the way the context is treated 😅
ItsTeegj
ItsTeegj•6mo ago
I was running into the same issue, but I believe I have a working solution to your problem. I am using KV, instead of D1, but it should work for you too.
No description
No description
ItsTeegj
ItsTeegj•6mo ago
Hopefully I am not too late in showing you this example.
mihaaai
mihaaaiOP•6mo ago
Interesting, you're always welcome, never too late 😄 It's very late for me so I can't test it right away, I'll let you know tomorrow or in a couple of hours. I was just wondering, the auth object is going to be recognized by the cli tool for migrate and generate commands? Since it's not explicitly exported I can't say it for sure right now.
ItsTeegj
ItsTeegj•6mo ago
Im not sure about the cli tool for migrate and generate since I was never able to get them working because I am using Drizzle. I just manually implemented the schemas from the documentation. As far as migrating, I use drizzle to handle the migration since according to the docs, better-auth migrate only works with kysely adapter anyway. I am able to use the auth client in my React app with no issues with this current setup. Let me know if you have any other questions or issues and I will see if I can help!
mihaaai
mihaaaiOP•6mo ago
Much appreciated! I'll let you know if worked for me as well, have a great day!
ItsTeegj
ItsTeegj•6mo ago
No problem. You have a great day as well!
mihaaai
mihaaaiOP•6mo ago
Sooo, I tried this middleware and works as expected for routes, the only problem is that I still cannot make the CLI pick up the auth since it's not exported according to the docs request, I don't use an ORM so this feature is essential
ItsTeegj
ItsTeegj•6mo ago
Im glad you were able to get the routes working. As far as the CLI, im not sure how to get those working with this setup. Might be worth asking in the general chat for help since its essential for your workflow.
bekacru
bekacru•6mo ago
The issue with the CLI is that it tries to run your config and connect to the database for migrations, but it needs the Hono context to do that in this case. One way potentially to solve it could be adding a flag to load auth.ts file just for the CLI. That way, you can reuse the config between the CLI and your app 
const getConfig = (ctx?: Context) => {
    return {
          database: ctx ? /* use the ctx if it's there */ : process.env.DB
        } satisfies BetterAuthOptions
}

export const auth = betterAuth(getConfig());

export const initAuth = (ctx) => betterAuth(getConfig(ctx));
const getConfig = (ctx?: Context) => {
    return {
          database: ctx ? /* use the ctx if it's there */ : process.env.DB
        } satisfies BetterAuthOptions
}

export const auth = betterAuth(getConfig());

export const initAuth = (ctx) => betterAuth(getConfig(ctx));
This might be able to solve it but may not work at all
mihaaai
mihaaaiOP•6mo ago
Thanks for tips but unfortunately this won't work with the CLI because there is no way to reference the D1 Database from outside the context, so the fallback to process.env.DB will return undefined when requesting the config from the CLI and commands will crash trying to .prepare(compiledQuery.sql) of undefined. I also tried to reference the local file through better-sqlite3 as a fallback but other Cloudflare specific environment (about the path module polyfills I think) are crashing the execution due to module incompatibility. I opened a GH issue to keep track of more about this topic
bekacru
bekacru•6mo ago
hey I think for this you could just use an endpoint that runs the migrations for you 
import { getMigrations } from 'better-auth/db';

export default app.get("/auth-migrate", async(ctx) => {
  const auth = getAuth(ctx)
  const { toBeCreated, toBeAdded, runMigrations } = await getMigrations(auth.options)
  if (!toBeCreated.length && !toBeAdded.length) {
    return 'No migrations to run'
  }
  await runMigrations()
  return 'Database migrations ran successfully'
})
import { getMigrations } from 'better-auth/db';

export default app.get("/auth-migrate", async(ctx) => {
  const auth = getAuth(ctx)
  const { toBeCreated, toBeAdded, runMigrations } = await getMigrations(auth.options)
  if (!toBeCreated.length && !toBeAdded.length) {
    return 'No migrations to run'
  }
  await runMigrations()
  return 'Database migrations ran successfully'
})

Did you find this page helpful?