-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(medusa, modules-sdk, types, utils): Re work modules loading and remove legacy functions #5496
Conversation
…remove legacy functions
🦋 Changeset detectedLatest commit: 37bdf52 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Ignored Deployments
|
…into feat/medusa-app-loading
…t/medusa-app-loading
@olivermrbl can you let me know if there is anything else to do on this one? I d like to get it merged so that we can finalise the search engine PR |
…into feat/medusa-app-loading
What
Make it possible to load all modules from a single entry point being the medusaApp. This includes few refactoring for unnecessary functions and cleanup. It will also in the future allow us to register modules that are not part of the internal definitions for custom modules.
NOTE
Since at the moment, some legacy modules depend on core services and resources and since the core services depend on the modules, they are cyclic dependencies, once the legacy modules are migrated, we will be able to move the modules loading before the services, the services won't need to have the getter for external modules since they will always be available