JROCBABY Posts - Answer Overflow

JROCBABY

•Created by JROCBABY on 3/22/2025 in #help

Double Slash in Path Causes ENOENT Error When Running Migrations in Docker

Hi everyone, I’m encountering an issue with Drizzle Kit when running migrations in a Docker container. The error occurs because Drizzle Kit is trying to read the 0000_snapshot.json file using a path with a double slash (//), like this: ENOENT: no such file or directory, open './/app/apps/my-app/src/drizzle/meta/0000_snapshot.json' The file exists at the correct path (/app/apps/my-app/src/drizzle/meta/0000_snapshot.json), but the double slash seems to be causing the issue. Here’s what I’ve tried so far: Verified that the schema.ts file is correct and the migration files are generated properly. Used path.resolve and path.normalize in drizzle.config.ts to ensure paths are correct. Confirmed that the snapshot file exists in the container at the expected location. Here’s my drizzle.config.ts:

Copy
import { defineConfig } from 'drizzle-kit';
import * as path from 'path';

const schemaPath = path.resolve(__dirname, './src/db/schema.ts');
const outPath = path.resolve(__dirname, './src/drizzle');

export default defineConfig({
  dialect: 'postgresql',
  schema: schemaPath,
  out: outPath,
  dbCredentials: {
    host: process.env.DB_HOST,
    port: Number(process.env.DB_PORT),
    user: process.env.DB_USER,
    password: process.env.DB_PASSWORD,
    database: process.env.DB_NAME,
    ssl: false,
  },
});

Copy
import { defineConfig } from 'drizzle-kit';
import * as path from 'path';

const schemaPath = path.resolve(__dirname, './src/db/schema.ts');
const outPath = path.resolve(__dirname, './src/drizzle');

export default defineConfig({
  dialect: 'postgresql',
  schema: schemaPath,
  out: outPath,
  dbCredentials: {
    host: process.env.DB_HOST,
    port: Number(process.env.DB_PORT),
    user: process.env.DB_USER,
    password: process.env.DB_PASSWORD,
    database: process.env.DB_NAME,
    ssl: false,
  },
});

And here’s the relevant part of my docker-compose.yml:

Copy
command: >
  sh -c "cd /app/apps/my-app &&
         bunx drizzle-kit generate --config drizzle.config.ts &&
         bunx drizzle-kit migrate"

Copy
command: >
  sh -c "cd /app/apps/my-app &&
         bunx drizzle-kit generate --config drizzle.config.ts &&
         bunx drizzle-kit migrate"

It seems to be caused by

 const raw2 = JSON.parse((0, import_fs.readFileSync)(./${it}).toString());

 const raw2 = JSON.parse((0, import_fs.readFileSync)(./${it}).toString());

Can't we fix it by doing

const raw2 = JSON.parse((0, import_fs.readFileSync)(path.normalize(`${it}`)).toString());

const raw2 = JSON.parse((0, import_fs.readFileSync)(path.normalize(`${it}`)).toString());

Has anyone encountered this issue before? Is there a way to prevent Drizzle Kit from introducing the double slash in the path? Any help would be greatly appreciated!

2 replies

DTDrizzle Team

•Created by JROCBABY on 3/21/2025 in #help

TypeScript Error: Circular Reference in Drizzle ORM Schema

Hey everyone, I’m getting TypeScript errors in my Drizzle ORM schema due to a circular reference. Here’s the code: typescript Copy Hey everyone, I’m getting TypeScript errors in my Drizzle ORM schema due to a circular reference. Here’s the code: typescript Copy

export const tableA = pgTable('tableA', {
  id: serial('id').primaryKey(),
  field1: text('field1').notNull(),
  field2: text('field2').notNull().unique(),
  field3: text('field3').notNull(),
  field4: text('field4').notNull(),
  field5: integer('field5').references(() => tableA.id), // Circular reference
});

export const tableA = pgTable('tableA', {
  id: serial('id').primaryKey(),
  field1: text('field1').notNull(),
  field2: text('field2').notNull().unique(),
  field3: text('field3').notNull(),
  field4: text('field4').notNull(),
  field5: integer('field5').references(() => tableA.id), // Circular reference
});

Errors:

TS7022: 'tableA' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

TS7024: Function implicitly has return type 'any' because it does not have a return type annotation and is referenced directly or indirectly in one of its return expressions.

TS7022: 'tableA' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

TS7024: Function implicitly has return type 'any' because it does not have a return type annotation and is referenced directly or indirectly in one of its return expressions.

What I’ve Tried: Using InferModel to infer the table type. Explicitly defining the table type with PgTableWithColumns. How can I properly type this schema to resolve the circular reference errors? Any help would be appreciated!

3 replies

Gaming

Programming