Vimes Comments - Answer Overflow

Vimes

Explore posts from servers

•Created by Vimes on 3/18/2025 in #help

Set active org on login

What would be the best way to find a users org based on ID. Since I run it as a before-session hook I can't use headers. auth.api.getFullOrganization expects a full org ID, but I don't have the ID yet. I'd need to somehow query for the org my user is a member of before I can use headers. The only solution I've found is to use SQL/Kysley, but htis seems insecure compared to the native API

6 replies

BABetter Auth

•Created by bayrem🪽 on 3/17/2025 in #help

One tap: Google One Tap is only available in browser environments

"Google One Tap is only available in browser environments" A server component does not run in a browser environment, it runs on the server. The browser just sees the results after it has run. I think you have to run this using "use client", remember that you can use "use client" on small (or large) parts of server pages / server components. But you can not use "use server" inside of a client component.

9 replies

BABetter Auth

•Created by bayrem🪽 on 3/17/2025 in #help

One tap: Google One Tap is only available in browser environments

are you running this on the client or the server? Ie does the code where you run this have "'use client" on the to of it?

9 replies

BABetter Auth

•Created by Vimes on 3/13/2025 in #help

How to securely host a pg DB for better auth

Dosen't seem like that would be very secure, allot of attacks come from AWS infra. The AWS I assume are at least partily dynamic (changing), which would require me to regularly manually update my IP list

11 replies

BABetter Auth

•Created by Vimes on 2/27/2025 in #help

Using Kysely with better auth

After a delete of node modules this started working. Can't get types for Pool from pg to work, but at least it works 🙂

11 replies

BABetter Auth

•Created by Vimes on 2/27/2025 in #help

Using Kysely with better auth

I tried something like this with a kysley.js

import type { DB } from "kysely-codegen";
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
import { Pool } from "pg";
import { Kysely, PostgresDialect } from "kysely";

const dialect = new PostgresDialect({
  // eslint-disable-next-line @typescript-eslint/no-unsafe-assignment,@typescript-eslint/no-unsafe-call
  pool: new Pool({
    user: "REDACTED",
    password: process.env.PG_PASSWORD,
    host: process.env.PG_URL,
    port: 5432,
    database: "REDACTED",
  }),
});


export const db = new Kysely<DB>({
  dialect,
});

import type { DB } from "kysely-codegen";
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
import { Pool } from "pg";
import { Kysely, PostgresDialect } from "kysely";

const dialect = new PostgresDialect({
  // eslint-disable-next-line @typescript-eslint/no-unsafe-assignment,@typescript-eslint/no-unsafe-call
  pool: new Pool({
    user: "REDACTED",
    password: process.env.PG_PASSWORD,
    host: process.env.PG_URL,
    port: 5432,
    database: "REDACTED",
  }),
});


export const db = new Kysely<DB>({
  dialect,
});

And calling my DB like this in auth.js

import { betterAuth } from "better-auth";
import { Pool } from "pg";
import { nextCookies } from "better-auth/next-js";
import { admin, organization } from "better-auth/plugins";
import { adminClient } from "better-auth/client/plugins";
import { db } from "./kysley";

export const auth = betterAuth({

  database: {
    db: db,
    type: "postgres" 
  },

  // database: db,
  emailAndPassword: {
    enabled: true,
  },
  emailVerification: {
    sendOnSignUp: true,
    autoSignInAfterVerification: true,
  },

  plugins: [organization(), admin(), adminClient(), nextCookies()],
});

import { betterAuth } from "better-auth";
import { Pool } from "pg";
import { nextCookies } from "better-auth/next-js";
import { admin, organization } from "better-auth/plugins";
import { adminClient } from "better-auth/client/plugins";
import { db } from "./kysley";

export const auth = betterAuth({

  database: {
    db: db,
    type: "postgres" 
  },

  // database: db,
  emailAndPassword: {
    enabled: true,
  },
  emailVerification: {
    sendOnSignUp: true,
    autoSignInAfterVerification: true,
  },

  plugins: [organization(), admin(), adminClient(), nextCookies()],
});

but using this method better auth fails to connect to my DB, if I do the connection string directly it works

11 replies

BABetter Auth

•Created by Vimes on 2/27/2025 in #help

Using Kysely with better auth

using kyseley seems OK enough, I managed to set it up and get it working with the DB in a project that dosen't use better auth My issue is getting the generated types from better auth. The docs seem to not mention anywhere where the better auth types are generated, I need to pass these to keysley. Or am I supposed to generate the DB types using keysley without better auth? The docs show me how to use adapters for prisma, I could change to prisma since it is at least clear how to use it. but I prefer Kyseley as I've used it before and like it. Docs say "The generate command creates the schema required by Better Auth. If you're using a database adapter like Prisma or Drizzle, this command will generate the right schema for your ORM. If you're using the built-in Kysely adapter, it will generate an SQL file you can run directly on your database." But I can't find this file, only a migrations file

11 replies

BABetter Auth

•Created by Vimes on 2/27/2025 in #help

Using Kysely with better auth

The docs dosen't include any info on how to use Kyseley. It seems like I should generate a sql file npx @better-auth/cli generate But what is this file called, where is it and how do I tie it to Kysley? I cna create a new Kysley instance like this it seems database: new Kysely({ dialect }), but I'd still somehow need to pass the types/schema to it, which I can generate but not find.

11 replies

BABetter Auth

•Created by Vimes on 2/27/2025 in #help

Using Kysely with better auth

thanks, I'll set it up manually or maybe just go for node-postgres

11 replies

TTCTheo's Typesafe Cult

•Created by SharpieMaster on 9/25/2023 in #questions

t3 app router when?

Just chime in, I decided to create a new project in NextJS app router with react server components It would have been done a long time ago if I just went the pages route instead, the amount of weird app-router bugs that require way to much time to debug is way too large

24 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 3/15/2023 in #questions

Zod with types from Supabase type gen

hmmm too bad, I'll just type it out by hand 🙂

3 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/23/2023 in #questions

Recommendations for auth setup

Not very sensitive data behind login, but only certain customers should see certain data. Supabase seems sweet because I can also use it for other stuff should the need arise (whatever I can use postgres and file storage for)

9 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/23/2023 in #questions

Recommendations for auth setup

I'm aware. right now I'm considering the free tier supabase, shuts down after one week of inactivity (which could happen during holidays) but github actions cron jobs seems to fix that

9 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/23/2023 in #questions

Recommendations for auth setup

It seems easier. But I also want a custom login screen (not possible with Auth0 at least) and the ability to easily programatically add data to users. Supabase seems simple enough to self host, haven't looked too much into firebase. oath2 providers could be an option, but only business will log inn and they expect email + password login

9 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/22/2023 in #questions

Type of return from await

Was just a carpenter having a smoke 🙃 Your solution worked @Geezer, thanks!

type Props = {
  audit: Audit;
};

type Audit = {
  content: {
    descendants: { items: ContentProps[] };
    id: string;
    level: number;
    name: string;
  };
};
export const getServerSideProps: GetServerSideProps = async (params) => {
  const audit = (await getAudit(
    `/granskninger/${params.query.slug as string}`
  )) as Audit;
  return {
    props: { audit },
  };
};

type Props = {
  audit: Audit;
};

type Audit = {
  content: {
    descendants: { items: ContentProps[] };
    id: string;
    level: number;
    name: string;
  };
};
export const getServerSideProps: GetServerSideProps = async (params) => {
  const audit = (await getAudit(
    `/granskninger/${params.query.slug as string}`
  )) as Audit;
  return {
    props: { audit },
  };
};

So I say audit = waiting for something sent as string -> this await returns the data that fits Audit props. still weird how I couldn't use just Props directly, but it probably makes sense somehow

25 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/22/2023 in #questions

Type of return from await

fire alarm going, be back in not too long

25 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/22/2023 in #questions

Type of return from await

TS not happy with audit as it's own thing. Currently chewing through geezers suggestion, allot to take inn

25 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/22/2023 in #questions

Type of return from await

how would audit: Audit work? Should I copy the props type to a different Audit type? @Geezer Give a few seconds/minutes to understand your code 🙂

25 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/22/2023 in #questions

Type of return from await

it will be a TS function once I become better at this TS thing

25 replies

TTCTheo's Typesafe Cult

•Created by Vimes on 2/22/2023 in #questions

Type of return from await

it is the data I'm using, but I am also very stupid so I may be wrong. Full file:

import { NextPage, GetServerSideProps } from "next";
import { ContentProps } from "../../../ts/auditTypes";
import Layout from "../../../components/Layout";
import { getAudit } from "../../api/auth/fetchData";
import AuditRenderer from "../../../audit/auditRenderer";
type Props = {
  audit: {
    content: {
      descendants: {  items: ContentProps[]; };
      id: string;
      level: number;
      name: string;

    };
  };
};



const Kundeportal: NextPage<Props> = ({ audit }) => {
  const { name } = audit.content;
  console.log("Audit er", audit);
  return (
    <Layout>
      <div className="container mx-auto px-4">
        <h1>{name}</h1>
        <AuditRenderer content={audit.content.descendants} />
      </div>
    </Layout>
  );
};

export const getServerSideProps: GetServerSideProps = async (params) => {


  const audit: Props = await getAudit(`/granskninger/${params.query.slug}`);
  return {
    props: { audit }
  };
};

export default Kundeportal;

import { NextPage, GetServerSideProps } from "next";
import { ContentProps } from "../../../ts/auditTypes";
import Layout from "../../../components/Layout";
import { getAudit } from "../../api/auth/fetchData";
import AuditRenderer from "../../../audit/auditRenderer";
type Props = {
  audit: {
    content: {
      descendants: {  items: ContentProps[]; };
      id: string;
      level: number;
      name: string;

    };
  };
};



const Kundeportal: NextPage<Props> = ({ audit }) => {
  const { name } = audit.content;
  console.log("Audit er", audit);
  return (
    <Layout>
      <div className="container mx-auto px-4">
        <h1>{name}</h1>
        <AuditRenderer content={audit.content.descendants} />
      </div>
    </Layout>
  );
};

export const getServerSideProps: GetServerSideProps = async (params) => {


  const audit: Props = await getAudit(`/granskninger/${params.query.slug}`);
  return {
    props: { audit }
  };
};

export default Kundeportal;

25 replies

Gaming

Programming