Medusa Project Structure: Where Every Kind of Code Belongs
Medusa loads code by convention. A directory-by-directory guide to what goes where, and the decision tree for placing any new piece of logic.
Articles tagged Medusa v2 — hands-on notes from the commerce builds we ship.
Medusa loads code by convention. A directory-by-directory guide to what goes where, and the decision tree for placing any new piece of logic.
The dashboard is a React app you can extend. Injecting widgets into existing pages, adding new routes, and the conventions that keep extensions from looking bolted on.
How Medusa's event bus works, when a subscriber is the right tool instead of a workflow step, and the retry semantics you need to design around.
When a module should become a plugin, how the package is structured, and what changes when your code has to run in someone else's application.
Everything in Medusa is resolved from a container. What is registered, how scoping works per request, and how to avoid the two mistakes that cause leaks.
Modules cannot reference each other's tables, so how do you attach a brand to a product? Links — and the query layer that reads across them.
Workflows are how Medusa keeps multi-step commerce operations from leaving your data half-written. How steps and compensation work, and how to build one properly.
Modules are the unit of everything in Medusa v2. What they are, why isolation matters, and how to build one that will not embarrass you in a year.
The install that works, the prerequisites people miss, and what to do in the first hour after the seed data loads.
Medusa is a TypeScript commerce framework you run yourself. Here is what that actually means, who it suits, who it does not, and how it differs from every hosted platform you have used.