MikroORM Fails to Connect After Upgrading Medusa from 2.8.3 to 2.11.13

[SarinSajuIqlytika]

In the Medusa.js docs it is recommended to bump from 2.8.3 to 2.11.13 to use newer features like media handling on product variants, so I updated the version of all @medusajs/* packages in package.json and then deleted package-lock.json and node_modules before running npm install --legacy-peer-deps. After a few warnings, the installation completed and node_modules was set up.

However, when running the migrations, MikroORM fails to connect. The project was working fine on 2.8.3 with the same configuration, and nothing in the database or MikroORM setup was changed. MikroORM only started acting up after the upgrade to 2.11.13.

Could you please guide me on how to fix this MikroORM connection issue after upgrading Medusa?

//package.json
{
"name": "livebhagwan",
"version": "0.0.1",
"description": "A starter for Medusa projects.",
"author": "Medusa (https://medusajs.com)",
"license": "MIT",
"keywords": [
"sqlite",
"postgres",
"typescript",
"ecommerce",
"headless",
"medusa"
],
"scripts": {
"build": "medusa build",
"seed": "medusa exec ./src/scripts/seed.ts",
"start": "medusa start",
"dev": "medusa develop",
"test:integration:http": "TEST_TYPE=integration:http NODE_OPTIONS=--experimental-vm-modules jest --silent=false --runInBand --forceExit",
"test:integration:modules": "TEST_TYPE=integration:modules NODE_OPTIONS=--experimental-vm-modules jest --silent=false --runInBand --forceExit",
"test:unit": "TEST_TYPE=unit NODE_OPTIONS=--experimental-vm-modules jest --silent --runInBand --forceExit"
},
"dependencies": {
"@google-cloud/storage": "^7.16.0",
"@medusajs/admin-sdk": "2.11.3",
"@medusajs/cli": "2.11.3",
"@medusajs/framework": "2.11.3",
"@medusajs/medusa": "2.11.3",
"@mikro-orm/core": "6.4.3",
"@mikro-orm/knex": "6.4.3",
"@mikro-orm/migrations": "6.4.3",
"@mikro-orm/postgresql": "6.4.3",
"awilix": "^8.0.1",
"express-fileupload": "^1.5.2",
"multer": "^2.0.2",
"pg": "^8.13.0",
"sweetalert2": "^11.22.5"
},
"devDependencies": {
"@medusajs/test-utils": "2.11.3",
"@mikro-orm/cli": "6.4.3",
"@swc/core": "1.5.7",
"@swc/jest": "^0.2.36",
"@types/jest": "^29.5.13",
"@types/node": "^20.0.0",
"@types/react": "^18.3.2",
"@types/react-dom": "^18.2.25",
"jest": "^29.7.0",
"prop-types": "^15.8.1",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"ts-node": "^10.9.2",
"typescript": "^5.6.2",
"vite": "^5.2.11",
"yalc": "^1.0.0-pre.53"
},
"engines": {
"node": ">=20"
}
}

//medusa-config.ts (.env is all setup fine)
import { loadEnv, defineConfig } from '@medusajs/framework/utils'

loadEnv(process.env.NODE_ENV || 'development', process.cwd())
module.exports = defineConfig({
projectConfig: {
databaseUrl: process.env.DATABASE_URL,
http: {
storeCors: process.env.STORE_CORS!,
adminCors: process.env.ADMIN_CORS!,
authCors: process.env.AUTH_CORS!,
jwtSecret: process.env.JWT_SECRET || "supersecret",
cookieSecret: process.env.COOKIE_SECRET || "supersecret",
},
// cookieOptions: { secure: false },
cookieOptions: { secure: false, sameSite: "lax", },
},
admin: {
backendUrl: process.env.MEDUSA_BACKEND_URL
},
modules: [
{
resolve: './src/modules/CMS'
},
{
resolve: "./src/modules/digital-product",
},
{
resolve: "@medusajs/medusa/file",
options: {
providers: [
{
resolve: "@medusajs/medusa/file-s3",
id: "s3",
options: {
file_url: process.env.S3_FILE_URL,
access_key_id: process.env.S3_ACCESS_KEY_ID,
secret_access_key: process.env.S3_SECRET_ACCESS_KEY,
region: process.env.S3_REGION,
bucket: process.env.S3_BUCKET_PUBLIC,
endpoint: process.env.S3_ENDPOINT,
// other options as needed
},
},
],
},
},
]
})

[SarinSajuIqlytika]

https://docs.medusajs.com/learn/codemods/replace-imports has all the solutions which worked for me