bknd types command errors on type import

[shishantbiswas]

I'm using the bknd types --outfile bknd-types.d.ts to create types but it error when importing a type without the type keyword in the import statement

[cameronapak]

Hey, this may help: https://docs.bknd.io/usage/cli/#using-configuration-file-bkndconfig

Can you try:

npx tsx node_modules/.bin/bknd types --outfile bknd-types.d.ts

[shishantbiswas]

Interesting, the command you gave me works even on import { RuntimeBkndConfig } from "bknd/adapter";, is this intended behaviour I was using it with bun so I didn't thought a ts related error would happen

[cameronapak]

...maybe try npx tsx bknd user create (you have to use npx tsx or node --experimental-strip-types node_modules/.bin/bknd because bun somehow doesn‘t work with the hashing on CLI. I couldnt track that down, it just stops with no message)
— Dennis via Discord

I think it's just a known bug that Bknd has an issue picking up a TS Bknd config via CLI. Now sure why this alternate approach works, but it does.

Other Discord comments that may be relevant:

• https://discord.com/channels/1308395750564302952/1308395751281393696/1380136556832231485
• https://discord.com/channels/1308395750564302952/1406265687344939008/1406332746032222339
• https://discord.com/channels/1308395750564302952/1446597986909028491/1446632672121196727

This is very much an issue I wish we could figure out, but I hadn't put time into it yet. I'm sure Dennis has put time into it but hasn't yet landed on a solution outside of the npx tsx approach

[cameronapak]

I found another way:

bun node_modules/.bin/bknd types --outfile bknd-types.d.ts

[shishantbiswas]

I found another way:

bun node_modules/.bin/bknd types --outfile bknd-types.d.ts

it seems to be database sensitive since node:sqlite isn't available in bun it crashed, I was doing connection: { url: "file:data.db" } for db

[cameronapak]

@shishantbiswas can you share your bknd.config.ts file?

[shishantbiswas]

import { em, entity, text, boolean } from "bknd";

import { registerLocalMediaAdapter } from "bknd/adapter/node";
import { RuntimeBkndConfig } from "bknd/adapter";

const local = registerLocalMediaAdapter();
// let html = await readFile("./index.html", "utf-8");

const schema = em({
  todos: entity("todos", {
    title: text(),
    done: boolean(),
  }),
});

// register your schema to get automatic type completion
type Database = (typeof schema)["DB"];
declare module "bknd" {
  interface DB extends Database {}
}

export default {
  connection: {
    url: "file:data.db",
  },
  options: {
    seed: async (ctx) => {
      await ctx.em.mutator("todos").insertMany([
        { title: "Learn bknd", done: true },
        { title: "Build something cool", done: false },
      ]);

      await ctx.app.module.auth.createUser({
        email: "test@bknd.io",
        password: "12345678",
      });
    },
  },
  config: {
    data: schema.toJSON(),
    auth: {
      enabled: true,
      jwt: {
        alg: "HS256",
        secret: "e79f40806aee76b95f0e2e5789eea",
      },
    },
    media: {
      enabled: true,
      adapter: local({
        path: "./public/uploads",
      }),
    },
  },
  adminOptions: {
    adminBasepath: "/admin/",
    assetsPath: "/admin/",
  },
} satisfies RuntimeBkndConfig;

[cameronapak]

Yeah, you're right.

import { registerLocalMediaAdapter } from "bknd/adapter/node";

Update: (added word might): This might fall back to Node for the node:sqlite

[shishantbiswas]

oh man, I been copy pasting this file so much in my tests cases that I totally overlooked such a trivial blunder on my end I wasn't even using/testing media

[cameronapak]

Sorry I'm not actually confident it was the media adapter that touched node:sqlite. I do however think what you said was correct that url: "file:data.db" uses node:sqlite

[cameronapak]

This is related to #354