Do migrations work in Electron?

[VitorAndrey]

Hi everyone, thanks for your time and support in advance.

I've come across some topics about migrations with Electron, but I'm still not sure how to proceed. I'm sorry if this is a trivial question, but how can I make it work? I'm using Electron-vite for scaffolding the project, and in development, it works.
But then it throws an error after the build:

Error: Can't find meta/_journal.json file at readMigrationFiles

drizzle.config.ts:

import type { Config } from 'drizzle-kit'

export default {
  schema: './src/database/schemas/!(exports).ts',
  out: './src/database/migrations',
  driver: 'better-sqlite'
} satisfies Config

src/database/index.ts:

import { drizzle } from 'drizzle-orm/better-sqlite3'
import { migrate } from 'drizzle-orm/better-sqlite3/migrator'
import Database from 'better-sqlite3'
import { dbPath } from './db-path'

import * as productSchema from './schemas/product'

const betterSqlite = new Database(dbPath)
const db = drizzle(betterSqlite, { schema: { ...productSchema } })

migrate(db, { migrationsFolder: 'src/database/migrations' })

export { db }

error: 
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Can't find meta/_journal.json file
at readMigrationFiles
(C:\Users\vitor\AppData\Local\Temp\2c5Ed9Qx4OlrkQZpC5qycYknJCU\resources\app.a..11)
at Object.migrate
(C:\Users\vitor\AppData\Local\Temp\2c5Ed9Qx4OIrkQZpC5qycYknJCU\resources\app.a...61)
at Object. < anonymous>
C\Users\vitor\AppData\Local\Temp\2c5Ed9Qx4OlrkQZpC5qycYknJCU\resources\app.a...10)
at Module._compile (node:internal/modules/cjs/loader:1271:14)
at Module. _extensions.js (node:internal/modules/cjs/loader:1326:10)
at Module.load (node:internal/modules/cjs/loader:1126:32)
at Module.load (node:internal/modules/cjs/loader:967:12)
at c. load (node:electron/js2c/node_init:2:13672)
at node:electron/js2c/browser_init:2:119675
at node:electron/js2c/bropvser_init:2;119884

[deadcoder0904]

@VitorAndrey you have to find a way to run the migrations script in electron before the build process runs.

i was having similar issues with docker container on production build but i fixed them.

you can take a look at it here -> https://github.com/deadcoder0904/easypanel-nextjs-sqlite

make sure to look at previous commits if you are not interested in how i'm doing things with docker (which is complicated if you don't know docker) but the previous commits include just scripts in package.json which i used to run to find those migration files. its not a direct answer but the solution is tangential.

[lucasrabiec]

This can be solved by attaching a migrations directory to your electron files during the build process. Then you can point to the extras/resources directory after the app unpacks it. This directory is accessible by user so if you have some sensitive data in your migrations it will not be a good solution.

[Your-Ehsan]

I did in this way in the main process

const migrationPath = import.meta.env.DEV
  ? 'resources/database/migrations'
  : join(__dirname, '../../resources/database/migrations')

And it works for me.