Tools/Notes
1
0
Fork 0
mirror of https://github.com/TriliumNext/Notes.git synced 2025-10-31 21:11:30 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(server): migration not working

Browse Source
This commit is contained in:
Elian Doran 2025-04-28 10:02:20 +03:00
parent 729ea1d2bc
commit d74b8e65bd
No known key found for this signature in database
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
apps/server/src/services/migration.ts
View File

@ -7,6 +7,7 @@ import resourceDir from "./resource_dir.js";
import appInfo from "./app_info.js"; import appInfo from "./app_info.js";
import cls from "./cls.js"; import cls from "./cls.js";
import { t } from "i18next"; import { t } from "i18next";
import { join } from "path";
interface MigrationInfo { interface MigrationInfo {
dbVersion: number; 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). // 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. // As such we have to preload the ESM.
// Going back to the original approach but making it webpack-compatible // 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; migration.module = (await import(importPath)).default;
} }