From d74b8e65bdaddb70508cf97ffac9e1e4e8b0a479 Mon Sep 17 00:00:00 2001
From: Elian Doran <contact@eliandoran.me>
Date: Mon, 28 Apr 2025 10:02:20 +0300
Subject: [PATCH] fix(server): migration not working

---
 apps/server/src/services/migration.ts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/apps/server/src/services/migration.ts b/apps/server/src/services/migration.ts
index c39fc9e2a..3b0d3dbfd 100644
--- a/apps/server/src/services/migration.ts
+++ b/apps/server/src/services/migration.ts
@@ -7,6 +7,7 @@ import resourceDir from "./resource_dir.js";
 import appInfo from "./app_info.js";
 import cls from "./cls.js";
 import { t } from "i18next";
+import { join } from "path";
 
 interface MigrationInfo {
     dbVersion: number;
@@ -99,7 +100,7 @@ async function prepareMigrations(currentDbVersion: number): Promise<MigrationInf
                 // Due to ESM imports, the migration file needs to be imported asynchronously and thus cannot be loaded at migration time (since migration is not asynchronous).
                 // As such we have to preload the ESM.
                 // Going back to the original approach but making it webpack-compatible
-                const importPath = `../../db/migrations/${file}`;
+                const importPath = join(resourceDir.MIGRATIONS_DIR, file);
                 migration.module = (await import(importPath)).default;
             }