fix: Check for existence of modules when seeding default data

[sradevski]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 2, 2024 8:33am

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)			Aug 2, 2024 8:33am
api-reference-v2	⬜️ Ignored (Inspect)			Aug 2, 2024 8:33am
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Aug 2, 2024 8:33am
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Aug 2, 2024 8:33am
medusa-docs	⬜️ Ignored (Inspect)			Aug 2, 2024 8:33am
resources-docs	⬜️ Ignored (Inspect)			Aug 2, 2024 8:33am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5124a13

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[adrien2p]

LGTM, eventually I would add allowUnregistered on the resolve just for extra precaution :)

[riqwan]

lgtm, whats the use-case for this one?

note: might be worth adding a console.warn

[sradevski]

@riqwan the default workflow runs on startup, but in platform I am not using the sales channels and stores modules, so it crashes.