Skip to content

Releases: medusajs/medusa

v2.0.6-preview

27 Aug 14:40
@olivermrbl olivermrbl
v2.0.6-preview
ac18b5d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.6-preview

Highlights

Introduced identity registration in auth domain

🚧 Breaking change

We have separated identity registration from authentication. For context about why this decision was made see #8683.

Introduced endpoint /auth/[scope]/[provider]/register

We have added an endpoint specifically for registering new identities. This change will only be used by providers that require registration, such as email-password.

Introduced method register in auth provider and auth module

We have introduced a new method register to the auth provider and auth module interfaces. This change will only be used by providers that require registration, such as email-password.

Examples of new authentication flows

Sign up with email-password:

POST /admin/invites -> admin creates invite
POST /auth/user/emailpass/register -> user registers identity
POST /admin/invites/accept -> invite is accepted passing the invite + auth token

Sign in with email-password:

POST /auth/user/emailpass -> authenticate with email-password
GET /admin/users/me -> get authenticated user

Sign up with Google:

POST /auth/user/google -> redirects to Google auth
POST /auth/user/google/callback -> Google hits callback URL, authenticates, and responds with user
POST /admin/invites/accept -> invite is accepted passing the invite + auth token

Sign up with Google:

POST /auth/user/google -> redirects to Google auth
POST /auth/user/google/callback -> Google hits callback URL, authenticates, and responds with user
GET /admin/users/me -> get authenticated user

Sign up as customer with email-password:

POST /auth/customer/emailpass/register -> customer registers identity
POST /store/customers -> customer is created

Sign in with email-password:

POST /auth/customer/emailpass -> authenticate customer with email-password

CLI commands to manage database operations

We have added a new namespace to our CLI specifically for database operations db:.

Alongside the namespace, a range of new commands have been introduced:

  • db:create: The command creates the database (if it is missing) and updates the .env file
  • db:migrate: This command will run the migrations and sync the links, unless --skip-links flag is specified
  • db:rollback: Rolls-back last batch of migrations for one or more selected modules
  • db:generate: Generates migrations for one or more selected modules
  • db:sync-links: Ensures links between modules are in sync

Events

We have (re)introduced events in the product domain:

"product-category.created"
"product-category.updated"
"product-category.deleted"
"product-collection.created"
"product-collection.updated"
"product-collection.deleted"
"product-variant.updated"
"product-variant.created"
"product-variant.deleted"
"product.updated"
"product.created"
"product.deleted"

Documentation: Redesign completed

We have completed redesigning our documentation for Medusa 2.0, which includes an updated layout and a range of new components improving the overall user experience.

Explore the updated documentation here.

Documentation: Re-introduced AI assistant (beta)

We have (re)introduced our AI assistant for Medusa 2.0 to help guide you through our documentation and find what you are looking for as fast as possible.

Try out the new AI assistant here.

Features

  • feat(dashboard): Hitting escape restores previous value by @kasperkristensen in #8654
  • feat(workflows-sdk): log on error by @carlos-r-l-rodrigues in #8666
  • feat(dashboard,core-flows,js-sdk,types,link-modules,payment): ability to copy payment link by @riqwan in #8630
  • feat(dashboard): Wrap each route in an ErrorBoundary by @kasperkristensen in #8674
  • feat(core-flows): create or update payment collections in RMA flows by @riqwan in #8676
  • feat(dashboard,core-flows,js-sdk,types): ability to mark payment as paid by @riqwan in #8679
  • feat(dashboard,core-flows): ability to refund payment post RMA flow by @riqwan in #8685
  • fix(core-flows): account for unfulfilled items while generating order status by @riqwan in #8698
  • feat(dashboard): add activities for order - claim, exchange, payment by @riqwan in #8702
  • feat(core-flows): order edit request by @carlos-r-l-rodrigues in #8705
  • chore(order): align mikroorm <> order module by @riqwan in #8710
  • feat(fulfillment,order): add created_by fields to fulfillment, return, claim, exchange by @riqwan in #8711
  • feat(medusa,types,core-flows): apply created_by values - claims, exchanges, returns, fulfillment by @riqwan in #8712
  • feat: add missing crud to provider identity service by @christiananese in #8717
  • feat(utils): use dotenv-expand to allow variables within env by @shahednasser in #8720
  • feat(dashboard): order edit UI by @fPolic in #8700
  • feat(core-flows,dashboard): adds item validations for claims, returns and exchanges by @riqwan in #8735
  • feat(create-medusa-app): set database name to project name by @shahednasser in #8727
  • feat(dashboard,types): add active order change panel - claims, exchanges & returns by @riqwan in #8738
  • feat: add env editor utility to edit update .env files by @thetutlage in #8741
  • feature: add db:create command by @thetutlage in #8760
  • fix(dashboard): summary section return fixes by @fPolic in #8770
  • feat: add sync links command by @thetutlage in #8775
  • feat: move migrations commands to the new db namespace by @thetutlage in #8810
  • feat: create auth provider identity by @christiananese in #8675
  • feat: Separate registration from authentication in auth domain by @olivermrbl in #8683
  • feat(dashboard): cancel return request by @fPolic in #8761

Bugs

Documentation

Read more

Contributors

Alexnortung, thetutlage, and 12 other contributors
Assets 2
Loading

v1.20.10

26 Aug 11:41
@olivermrbl olivermrbl
1.20.10
de1417e
Compare
Choose a tag to compare
v1.20.10

Bugs

  • fix: Pass in data to PATCH call so cart amount is updated on quantity change by @Arsenalist in #8456
  • fix(admin-ui): Fixed DropdownMenu inside a Modal zIndex issues by @adevinwild in #8358
  • fix: Check if the SalesChannels FF is enabled on /admin/products by @adevinwild in #8357

Docs

New Contributors

Full Changelog: v1.20.9...1.20.10

Contributors

Arsenalist, MuhammadElsaeed, and adevinwild
Assets 2
Loading

v2.0.5-preview

19 Aug 10:50
@olivermrbl olivermrbl
v2.0.5-preview
a77c23c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.5-preview

Highlights

Product Category organizer component

We've polished the Product Category organizer component for a smoother drag-and-drop experience. As part of the polish, we've also fixed an issue with a dependency.

Email-pass as default authentication provider

🚧 Breaking change

We've updated the default modules config to include email-password as a default authentication provider. This is a breaking change. To ensure your application will continue to run, you should install the preview version of the email-password provider package:

yarn add @medusajs/auth-emailpass@preview

Workflows Reference

We've introduced a reference of all workflows used in Medusa's core. It includes a visual representation of steps, hooks, and conditionals.

Explore the reference here.

Features

  • feat: admin return reason list by @christiananese in #8482
  • feat(medusa): filter shipping options by location by @riqwan in #8511
  • feat(dashboard,js-sdk,types): ability to add refund reason and note by @riqwan in #8466
  • feat(types,dashboard): ability to set shipping methods for claim by @riqwan in #8533
  • feat: create return reason by @christiananese in #8516
  • feat(create-medusa-app): prompt for database name with credentials by @shahednasser in #8552
  • feat(core-flows,dashboard,medusa): fixes set of tiny bugs in claims flow by @riqwan in #8551
  • feat(dashboard): BulkEditor Boolean cell behaviour by @kasperkristensen in #8418
  • feat: Move userpass default definition to defineConfig instead of a hard-coded value by @sradevski in #8557
  • feat(core-flows): introduce a generic create entities step by @riqwan in #8553
  • feat(medusa-oas-cli): automatically fix missing circular references by @shahednasser in #8600
  • feat(core-flow): order edit endpoints by @carlos-r-l-rodrigues in #8596
  • feat(dashboard,core-flows,js-sdk,types,medusa): Add exchange UI + fixes by @riqwan in #8606
  • feat(medusa,core-flows,types): API to create payment collections for order by @riqwan in #8617

Bugs

Documentation

Chores

  • chore: normalize packages version by @carlos-r-l-rodrigues in #8492
  • chore(core-flows): [4] export types and types, add basic TSDocs by @shahednasser in #8509
  • chore(core-flows): [3] export types and types, add basic TSDocs by @shahednasser in #8507
  • chore(core-flows): [2] export types and types, add basic TSDocs by @shahednasser in #8505
  • chore(core-flows): [5] export types and types, add basic TSDocs by @shahednasser in #8510
  • chore(core-flows): [6] export types and types, add basic TSDocs by @shahednasser in #8512
  • chore(core-flows): [7] export types and types, add basic TSDocs by @shahednasser in #8514
  • chore(core-flows): [8] export types and types, add basic TSDocs by @shahednasser in #8517
  • chore(core-flows): [9] export types and types, add basic TSDocs by @shahednasser in #8519
  • chore(core-flows): [11] export types and types, add basic TSDocs by @shahednasser in #8521
  • chore(core-flows): [12] export types and types, add basic TSDocs by @shahednasser in #8522
  • chore(core-flows): [14] export types and steps, add basic TSDocs by @shahednasser in #8524
  • chore(core-flows): [16] export types and steps, add basic TSDocs by @shahednasser in #8527
  • chore(core-flows): [17] export types and steps, add basic TSDocs by @shahednasser in #8528
  • chore(core-flows): [18/18] export types and types, add basic TSDocs by @shahednasser in #8529
  • chore(order): item update quantity by @carlos-r-l-rodrigue...
Read more

Contributors

thetutlage, sradevski, and 7 other contributors
Assets 2
Loading

v2.0.4-preview

08 Aug 13:35
@olivermrbl olivermrbl
v2.0.4-preview
73cc669
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.4-preview

Highlights

Domain-specific Workflow Hooks

We recently introduced Workflow Hooks, allowing you to expose injection points in workflows for the consumer to perform custom logic.

Among Medusa's core workflows, you will find available hooks in the following domains:

  • Products: create, update, and delete
  • Orders: create, cancel, complete, create fulfillment, cancel fulfillment, and create shipment
  • Promotions: create, update, delete, create campaign, update campaign, and delete campaign
  • Carts: create and update
  • Customers: create, update, delete, create address, update address, and delete address

Workflow hooks are consumed by registering a hook handler on the workflow. The hook handlers should be placed and registered in the /workflows/hooks folder of your Medusa project. For example, here's how to use the product-created hook:

// workflows/hooks/product-created.ts
import { createProductsWorkflow } from "@medusajs/core-flows"

createProductsWorkflow.hooks.productCreated(( { products, additional_data }) => {
  // run custom business logic
})

This hook receives the created products and arbitrary additional_data. The latter should be passed to the workflow upon running it:

await createProductsWorkflow(req.scope).run({
  input: { products: [ ... ], additional_data: { ... } },
})

In combination with extending the request payload to receive additional data, you can achieve a range of different use cases with Workflow Hooks, e.g. linking a product with another resource. We will share recipes for many of these cases in the near future.

We will continuously add more Workflow Hooks to our core workflow, e.g. a hook to transform line item data and price before it's added to the cart. Keep an eye out for our preview release updates, as they will contain an overview of the new hooks.

Features

Bugs

Documentation

Chores

New Contributors

Full Changelog: v2.0.3-preview...v2.0.4-preview

Contributors

thetutlage, letalumil, and 7 other contributors
Assets 2
Loading

v2.0.3-preview

02 Aug 15:57
@olivermrbl olivermrbl
v2.0.3-preview
4b0119f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.3-preview

Get started with a new project

To get started using the preview release, run the following command:

npx create-medusa-app@preview

This command will create a new Medusa project with our redesigned admin and a 2.0-compatible Next.js storefront. The Medusa application and the Next.js storefront are separate projects in separate folders.

Highlights

Workflow Hooks

🚧 Breaking change

We have added a new helper, createHook, to the workflows-sdk. The createHook helper exposes a hook from a workflow. Later (after the workflow has been composed), the workflow consumers can bind a handler to the hook to run custom logic.

Note

As of now, you can only register one hook handler, and the workflow orchestrator ignores the return value.

Exposing hook via createHook

import {
  createStep,
  createHook,
  createWorkflow,
  WorkflowResponse
} from '@medusajs/workflows-sdk'

const createProductStep = createStep('createProduct', function () {
  // business logic for "createProduct"
})

const workflow = createWorkflow('name', function (input) {
  createProductStep(input)
  const productCreatedHook = createHook('productCreated', { productId: input.id })

  return new WorkflowResponse(input, {
    hooks: [productCreatedHook]
  })
})

Points to note

  • Unlike the createStep function, the createHook method is called within the workflow composition callback.
  • You must return the created hooks from the composition callback. Returning of hooks is needed for the TypeScript engine to provide intellisense when registering a handler for the hook.
  • Hooks are executed in the same position as they are defined within the composition callback

Registering the hook handler
The workflow user must register a hook handler to run custom logic within a workflow. They can do that as follows.

workflow.hooks.productCreated(() => {
  // run custom business logic
})

Points to note

  • The hook handler behaves similarly to a workflow step. It can run async code, will be retried, and can also have compensation behavior (defined as the 2nd parameter)
  • There can only be one handler for a hook. If you need multiple handlers, you should create another workflow and register that as the hook handler (not supported yet).
  • The return value of the hook handler is ignored in this first iteration.

Introducing the WorkflowResponse class and breaking changes

The introduction of hooks has changed the return value of the createWorkflow composition callback. Now, we must return both the workflow results and the configured hooks.

Instead of manually composing the return value, you can use the WorkflowResponse class to construct the current response. The WorkflowResponse class accepts the following parameters.

  • The first parameter is the result of the workflow.
  • The second parameter (optional) is a config object with configured hooks.

Product Import and Export

We have re-introduced Product Import and Export and simultaneously redesigned the notifications drawer in the dashboard.

Right now, we are polling for new notifications every third second, but we intend to introduce SSE (or a similar tech.) to enable real-time notifications.

Product Tag management UI

We have added Product Tag management in the dashboard. Find it in "Settings > Product Tags".

New Recipes: Subscriptions and Digital Products

We have added two new recipes covering how to add support for Subscriptions and Digital Product respectively. They both come with an example repository.

Check out the Subscription recipe here.

Check out the Digital Products recipe here.

Features

Bugs

Documentation

Read more

Contributors

thetutlage, sradevski, and 9 other contributors
Assets 2
Loading

v1.20.9

29 Jul 11:45
@olivermrbl olivermrbl
v1.20.9
4fedaae
Compare
Choose a tag to compare
v1.20.9

Fixes

Full Changelog: v1.20.8...v1.20.9

Contributors

Arsenalist, pepijn-vanvlaanderen, and kasperkristensen
Assets 2
Loading

v2.0.2-preview

25 Jul 15:44
@olivermrbl olivermrbl
v2.0.2-preview
eb64ae7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.2-preview

Get started with a new project

To get started using the preview release, run the following command:

npx create-medusa-app@preview

This command will create a new Medusa project with our redesigned admin and a 2.0-compatible Next.js storefront. The Medusa application and the Next.js storefront are separate projects in separate folders.

Update existing project

Ensure your Medusa dependencies in package.json are using the preview tag:

{
  "dependencies": {
    "@medusajs/medusa": "preview",
    "@medusajs/pricing": "preview",
    "@medusajs/product": "preview",
    ...
  }
}

To ensure an upgrade to a new version is completed correctly, run the following sequence of commands:

rm -rf node_modules
rm yarn.lock // or package-lock.json

yarn // If you are using yarn berry, you need to create the lock-file first

Highlights

Migrations and Linking CLI

We have introduced new CLI commands for generating migrations and managing links between modules. The latter is used to ensure links are in sync.

To generate migrations in your module, you can run the following command:

npx medusa migrations generate <name of module>

To sync the links between modules, you can run the following command:

npx medusa links sync

In case your links are out of sync, you'll be guided through possible actions to take.

Explore our full CLI reference in our documentation.

New Middlewares API

🚧 Breaking change

We have introduced a new way of defining middlewares for API Routes. This is a breaking change.

Instead of exporting a config from middlewares.ts, you will now need to use a new utility function defineMiddlewares.

To upgrade your project, you should apply the following changes:

- import { MiddlewareConfig } from '@medusajs/medusa'
+ import { defineMiddlewares } from '@medusajs/medusa'

- export const config: MiddlewareConfig = {
-   routes: []
- }
+ export default defineMiddlewares({
+  routes: []
+ })

Read more about the new Middlewares API in our documentation.

Tax-inclusive Pricing

We have re-introduced tax-inclusive pricing. Tax-Inclusive pricing allows you to set the final prices for products and shipping options regardless of the customer's applicable tax rates. When tax-inclusive prices are used, Medusa automatically calculates the tax amount for a given price.

Read more about tax-inclusive pricing in our documentation.

Coming soon

The following are work-in-progress and will be released soon:

  • Returns, Exchanges, and Claims of Orders
  • Export and Import of Products
  • Bulk Editor improvements
  • Digital Products and Subscription Recipes

Features

Bugs

Read more

Contributors

thetutlage, sradevski, and 9 other contributors
Assets 2
Loading

v1.20.8

18 Jul 10:29
@olivermrbl olivermrbl
v1.20.8
33ecee4
Compare
Choose a tag to compare
v1.20.8

Features

Bugs

  • fix(create-medusa-app): ensure the latest create-next-app version is used by @shahednasser in #7806
  • fix: remove products from product collection type in generated references by @shahednasser in #7812
  • fix: Check if the SalesChannel FF is enabled before using it on the /admin/products/:id route by @adevinwild in #8120

Documentation

Chores

New Contributors

Full Changelog: v1.20.7...v1.20.8

Contributors

xyzones, gulshankumardev, and 8 other contributors
Assets 2
Loading

v2.0.1-preview

11 Jul 14:29
@olivermrbl olivermrbl
v2.0.1-preview
b5a44ef
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.1-preview

Get started with new project

To get started using the preview release, run the following command:

npx create-medusa-app@preview

This command will create a new Medusa project with our redesigned admin and a 2.0-compatible Next.js storefront. The Medusa application and the Next.js storefront are separate projects in separate folders.

Update existing project

Ensure your Medusa dependencies in package.json are using the preview tag:

{
  "dependencies": {
    "@medusajs/medusa": "preview",
    "@medusajs/pricing": "preview",
    "@medusajs/product": "preview",
    ...
  }
}

To ensure an upgrade to a new version is completed correctly, run the following sequence of commands:

rm -rf node_modules
rm yarn.lock // or package-lock.json

yarn // If you are using yarn berry, you need to create the lock-file first

Highlights

Migrations CLI

🚧 Breaking change

The migrations workflow and CLI output have changed. Here's a summary of the changes.

  • The commands remain the same as npx medusa migrations run and npx medusa migrations revert
  • The CLI output has been changed to be more visually appealing and add separate migrations logs for each module with a line break

Breaking changes

The revert command has a breaking change that it requires one or more module names to perform the revert. It means, the action revert is not valid at the global/app level. It must be executed on a specific module.

If you are developing a custom module, you can run the revert command for it as follows:

# helloWorld is the moduleName
npx medusa migrations revert helloWorld

When-then utility for conditional execution of steps in Workflows

We have added a new when-then utility to execute steps conditionally.

Here's a basic example of its usage within a workflow:

const workflow = createWorkflow("workflow", function (input) {
    
    const result = when(input, (input) => {
      return input.someConditionalData
    }).then(() => {
      const otherResult = someStep({ ... })
      return otherResult
    })

    return someOtherStep(result)
  }
)

Tax Regions UI update

The Tax Regions domain in Medusa Admin has been revamped, improving the overall UI and UX.

Features

Bugs

Documentation

Read more

Contributors

thetutlage, sradevski, and 9 other contributors
Assets 2
Loading

v2.0.0-preview

04 Jul 16:00
@olivermrbl olivermrbl
v2.0-preview
94e5fee
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.0-preview

Medusa 2.0 Public Preview Release

Today, we’re excited to share a Preview Release of Medusa 2.0.

The following document covers resources, guides, and things to know about the first preview release of Medusa 2.0. It will help you get started and give you a high-level overview of your new Medusa 2.0 application and what’s still to be done.

The preview release is not ready for production and is only intended for experimentation and development of new projects.

The release candidate later this year will include more fully-fledged resources for 2.0, including an overview of breaking changes, migration guides, and much more that will ensure a smoother onboarding.

We advise against upgrading your project to 2.0 at this point, as we are still working on documentating the best possible path.

These release notes are only intended to help you start and introduce you to your new Medusa 2.0 project. For a more in-depth exploration of the major upgrade, refer to our new documentation.

We are publishing this release to solicit early user and community feedback. Please file Issues for bug reports and/or submit Discussions with input or questions.

We thank you all very much in advance.

Get started

To get started using the preview release, run the following command:

npx create-medusa-app@preview

This command will create a new Medusa project with our redesigned admin and a 2.0-compatible Next.js storefront. The Medusa application and the Next.js storefront are separate projects in separate folders.

The folder structure of Medusa projects has changed:

my-project
 ├── src
 │   ├── admin
 │   ├── api
 │   ├── jobs
 │   ├── subscribers
-│   ├── services
-│   ├── models
-│   ├── migrations
-│   ├── loaders
+│   ├── modules
+│   │   └── my-module
+│   │       ├── loaders
+│   │       ├── migrations
+│   │       ├── models
+│   │       ├── index.ts
+│   │       └── service.ts
+│   ├── workflows
 └── medusa-config.ts

The modules folder replaces a lot of folders from a 1.0 project and will contain most business logic customizations in your Medusa 2.0 application. We highly encourage you to read the section of our docs covering this new concept in detail.

The workflows folder holds your custom workflows. Workflows are a fundamental concept in cross-module operations and a core element of Medusa 2.0. Read more about workflows here.

Additionally, medusa-config.js has been cleaned up and improved with a new type-safe utility function for defining the config for your Medusa project. The file can also now live as both a JS and TS file.

export default defineConfig({
  projectConfig: {
    http: {
      storeCors: "<STORE_CORS>",
      adminCors: "<ADMIN_CORS>",
      authCors: "<AUTH_CORS>"
    },
    redisUrl: "<REDIS URL>",
    databaseUrl: "<DATABASE_URL>",
  },
  admin: {
    backendUrl: "https://my-medusa-server.medusajs.app",
  },
})

You are now ready to explore all the new features in the preview release. However, we recommend reading through our documentation to fully understand what is new in 2.0 and how it differs from 1.0.

Additionally, you can find references and code snippets for our tools in our Learning Resources.

Keeping up with preview releases

We release preview versions every three hours. We recommend setting the version of your Medusa dependencies to preview, so you can regularly update without knowing specific version numbers.

All your Medusa dependencies in package.json should look something like this:

{
  "dependencies": {
    "@medusajs/medusa": "preview",
    "@medusajs/pricing": "preview",
    "@medusajs/product": "preview",
    ...
  }
}

To ensure an upgrade to a new version is completed correctly, run the following sequence of commands:

rm -rf node_modules
rm yarn.lock // or package-lock.json

yarn // If you are using yarn berry, you need to create the lock-file first

What’s new?

Medusa 2.0 is a huge upgrade, in fact, the biggest upgrade since we open-sourced the project four years ago. The upgrade comes with many new features and improvements, some of which are still work-in-progress. In the following sections, we will briefly cover these features and the parts of the product still subject to change. A more detailed changelog will be released as part of the release candidate and, subsequently, the official release later this year.

Admin dashboard

Our admin dashboard has been completely overhauled, improving its overall look and feel to provide end-users with a more cohesive and consistent experience.

Additionally, we have migrated away from Webpack to Vite, which improves the developer experience with features like HMR and allows us and our users to tap into a rich and flourishing community and plugin ecosystem.

Read more about the admin dashboard and its extension capabilities here.

A few admin flows have yet to be built. This is primarily around returns, exchanges, claims, and order edits. We expect to finalize these in the coming weeks.

Modules architecture

Our modules foundation has been re-architected to entirely decouple modules from one another, enabling greater composability, a new standalone usage mode, and a more approachable incremental adoption of Medusa.

Read more about the architecture refactor in our 2.0 announcement from earlier this year.

New commerce features

We saw reworking the module's architecture as an opportunity to rethink the feature set of some of the business domains in Medusa 1.x. As a result, we are excited to introduce a range of advanced capabilities across a series of modules. Here are a few noteworthy improvements:

  • Stock location: Build omnichannel experiences with new stock location features, including “Buy online, pick up in-store” options.
  • Inventory: Compose multi-part variants and share inventory across products with our new inventory management features
  • Authentication: Enable authentication with external providers, such as Google, with our new authentication and user management features
  • Promotion: Create granular promotions with our new rules engine. Use conditions to create bundled discounts, buy-get, spend-get, temporary campaigns, and more

Many other modules have also seen improvements. Browse through all of them in our learning resources.

Data modeling language

A core feature of Medusa is the ability to extend the default commerce application with additional business logic to cater to a specific use case, natively integrate with third-party providers, replace existing domains, and more.

At the core of extensions in Medusa 2.0 are modules, and at the core of modules are data models. Data models define the concepts living within your application. In our commerce modules, you find orders, products, customers, promotions, etc. By introducing your own data models, you extend this semantic layer of your application, enabling you to build features and custom workflows by integrating existing and new concepts. Because data models are at the core of every customization, we decided to make them easier to work with.

We are excited to announce a new data modeling language in Medusa 2.0 that will improve the experience of defining and working with data in your application. You can read more about the new feature here.

Below is a simple example of what data models will look like in 2.0:

Long-running Workflows

We are excited to extend our existing workflow capabilities with Long-running Workflows for processing long-running operations in the background. Instead of synchronously receiving a workflow's result, Long-running Workflows are subscribed to for status changes and execution progress. Additionally, the Long-running Workflows comes with an API for programmatically moving from one step to the next. These features make Long-running Workflows a great fit for use cases that require a human-in-the-loop or operations with a varying long-running execution time.

For example, we use Long-running Workflows extensively to build the infrastructure provisioning of Medusa Cloud.

Alongside the Long-running Workflows, we are also introducing a new admin section for managing them. Here, you can see currently executing and completed workflows, providing full transparency into your long-running operations.

Medusa 2.0 comes with much more than what is highlighted in this post. We will cover everything in-depth in the official release notes.

These release notes are published as a GitHub Discussion as well for comments and questions on the preview release.

Assets 2
Loading