Time for another release of Medusa!
Version 1.7 introduces a massive performance improvement, Module Resolution API, migrating the Medusa admin to Vite, and more!
Keep reading below to learn more about all the new changes in this release!
You can update your Medusa server using the following command:
npm install @medusajs/medusa@latest @medusajs/medusa-cli@latest medusa-interfaces@latest
Make sure to update any other Medusa plugins or packages you use!
You can check out the upgrade guide for breaking changes in this version and how to resolve them.
You can also update the Medusa Admin by pulling changes from the GitHub repository.
You can check out the upgrade guide for breaking changes in this new update and how to resolve them.
Medusa servers that have large traffic and carts with a lot of products previously suffered from a decrease in performance. This is due to issues related to algorithm complexity, event loop bottleneck, and a large number of calls to external API during the checkout flow.
This version fixes all these issues and more, which leads to a huge performance improvement of the entire core engine! After updating your server, the checkout flow on your store will be much faster, providing your customers with a better user experience.
When a guest customer places an order, then registers, they can now claim the order they placed as a guest by providing the order ID.
An email is then sent to the email address associated with the order with a link to confirm the customer’s request to claim the order.
You can learn more about implementing this flow in our documentation:
The Module Resolution API allows even more customization capabilities within Medusa. Modules represent function areas in the core engine, such as Inventory Management, Events system, Cache mechanism, etc…
This new API would allow developers to replace an entire domain to change how that domain works in Medusa.
The current version introduces the first steps in allowing customizations with Modules. Future versions would support replacing different function areas in the core.
Starting from version 1.7, you can use regular expression patterns for admin and storefront CORS configurations.
For example, you can use
*.example.com to allow all subdomains of
example.com to send requests to the server.
You can learn more in this documentation.
Medusa Admin was previously built with Gatsby. Gatsby is a great choice for building storefronts and websites in general. However, for the Medusa Admin, we weren’t fully utilizing its super powers. This took a toll on developer experience due to slow build processes.
We’ve now migrated from using Gatsby to using Vite 3 with React. This reduced the local build time by more than 10x the original time.
You can check the upgrade guide for details on breaking changes after this update and how to resolve them.
Aside from the major redesign of our documentation website, we have added more documentation pages. Some of the important ones are:
- Deploy Your Medusa Server to Railway
- Discounts Architecture Overview
- Manage Discounts using Admin APIs
- Use Discounts in Checkout
- How to Use CustomerGroup APIs
This week, we heavily focused our content on showcasing Medusa as a B2B ecommerce platform. As Medusa supports all B2B essential ecommerce features, and as Medusa is currently the #1 Node.js ecommerce server, it is one of the top B2B ecommerce platforms currently available.
This week, we’ve shared:
- B2B Perspective report
- 2-series tutorial on how to create a B2B ecommerce platform with Medusa
- Comparison between top 5 B2B ecommerce platforms
- 9 UX tips from the best B2B ecommerce website (as crowned by HackerNews)
Next week we’ll be sharing more tips for B2B ecommerce businesses. Be sure to look out for our new content! You can also subscribe to our newsletter here.
Should you have any issues or questions related to Medusa, then feel free to reach out to the Medusa team via Discord.