Errors when change drizzle adapter

[aklusa022]

Hello,
I am having issues switching the databases from neon to pg since I do not wish to use neon.

When trying to reconfigure the drizzle /src/db/index.ts to use just regular old drizzle-orm/postgres-js instead of neon-http, upon running build or when running in dev mode i get issues relating to the crypto module and tls modules not being found which is a strong indication that its trying to use server-side modules in a client-side browser environment....

Is this template that tightly integrated only around neon???

or is there steps to going to change it out?

This is what it comes with by default:

import { drizzle } from 'drizzle-orm/neon-http';

import { ENV } from "@/lib/env.server";

import * as schema from "./schema";

const sql = neon(ENV.DATABASE_URL);
export const db = drizzle({ client: sql, schema });

and this is what I tried to change it to

import { drizzle } from "drizzle-orm/postgres-js";
import postgres from "postgres";

import { ENV } from "@/lib/env.server";

import * as schema from "./schema";

const globalForDb = globalThis as unknown as {
	conn: postgres.Sql | undefined;
};

const conn = globalForDb.conn ?? postgres(ENV.DATABASE_URL);
if (ENV.NODE_ENV !== "production") globalForDb.conn = conn;

export const db = drizzle(conn, { schema });

please help :\\

[aklusa022]

A

[alexandretrotel]

I've seen the issue you opened! Indee, Zap.ts is strongly relying on the current stack and is planning to be more and more modular.

Thank you for sharing the issue!