[Bug]: Seeding issues seem related to crashing Settings pages

[22blaster]

Package.json file

{
  "name": "medusa-starter-default",
  "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 --runInBand --forceExit",
    "test:unit": "TEST_TYPE=unit NODE_OPTIONS=--experimental-vm-modules jest --silent --runInBand --forceExit"
  },
  "dependencies": {
    "@medusajs/admin-sdk": "2.1.3",
    "@medusajs/cli": "2.1.3",
    "@medusajs/framework": "2.1.3",
    "@medusajs/medusa": "2.1.3",
    "@mikro-orm/core": "5.9.7",
    "@mikro-orm/knex": "5.9.7",
    "@mikro-orm/migrations": "5.9.7",
    "@mikro-orm/postgresql": "5.9.7",
    "awilix": "^8.0.1",
    "pg": "^8.13.0"
  },
  "devDependencies": {
    "@medusajs/test-utils": "2.1.3",
    "@mikro-orm/cli": "5.9.7",
    "@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"
  },
  "engines": {
    "node": ">=20"
  }
}

Node.js version

v22.11.0

Database and its version

16.2

Operating system name and version

MacOS 12.7.6

Browser name

Chrome

What happended?

I tried a fresh install with this

npx create-medusa-app@latest --db-url {the-full-db-url-was-here} --with-nextjs-starter --verbose

and I noticed this during the install

✔ Created admin user
⠋ Seeding database...
info:    Executing script at ./src/scripts/seed.ts...
redisUrl not found. A fake redis instance will be used.
warn:    Local Event Bus installed. This is not recommended for production.
info:    Locking module: Using "in-memory" as default.
warn:    Link modules schema: No linkable key found for sales_channel_id on module sales_channel.
warn:    Link modules schema: No linkable key found for sales_channel_id on module sales_channel.
warn:    Link modules schema: No linkable key found for inventory_item_id on module inventory.
warn:    Link modules schema: No linkable key found for inventory_item_id on module inventory.
warn:    Link modules schema: No linkable key found for sales_channel_id on module sales_channel.
warn:    Link modules schema: No linkable key found for sales_channel_id on module sales_channel.
warn:    Link modules schema: No linkable key found for sales_channel_id on module sales_channel.
warn:    Link modules schema: No linkable key found for sales_channel_id on module sales_channel.
info:    No job to load from /Users/kimbo/work/clients/lobba/webdev/ploppy-local/ploppy/node_modules/@medusajs/medusa/dist/jobs. skipped.
info:    Seeding store data...
info:    Seeding region data...
info:    Finished seeding regions.
info:    Seeding tax regions...
info:    Finished seeding tax regions.
info:    Seeding stock location data...
info:    Seeding fulfillment data...
error:   Error running script
error:   Service with alias "service_zone" was not found.
{
~errors stuff~ 
clients/lobba/webdev/ploppy-local/ploppy/node_modules/@medusajs/core-flows/dist/fulfillment/workflows/create-shipping-options.js: [create-shipping-options-workflow -> validate-fulfillment-providers-step (invoke)]'
}
✔ Seeded database with demo data
✔ Finished Preparation
✔ Project Prepared
Starting Medusa...

I ran "npm run dev" and backend admin pages related to this error/warning messages seem to crash related to it. I did also try changing my NODE_ENV to development to see if that has any affect and it does not.

Expected behavior

• The db should have seeded data, eg. for products
• I should be able to visit the following x3 pages (all other pages load fine) without the page crashing and saying "500 - Internal server error. An unexpected error occurred on the server. Please try again later." and the console saying "Error: Service with alias "sales_channels" was not found."
  • http://localhost:9000/app/settings/publishable-api-keys
  • http://localhost:9000/app/settings/secret-api-keys
  • http://localhost:9000/app/settings/sales-channels

Actual behavior

• Seeded data doesnt seem to be available as I see no data in the database for products no in the admin dashboard
• When visiting the following x3 pages (all other pages load fine) the page crashes and says "500 - Internal server error. An unexpected error occurred on the server. Please try again later." and the console says "Error: Service with alias "sales_channels" was not found."
  • http://localhost:9000/app/settings/publishable-api-keys
  • http://localhost:9000/app/settings/secret-api-keys
  • http://localhost:9000/app/settings/sales-channels

Link to reproduction repo

https://github.com/medusajs/medusa