* docs: migrate ui docs to docs universe * created yarn workspace * added eslint and tsconfig configurations * fix eslint configurations * fixed eslint configurations * shared tailwind configurations * added shared ui package * added more shared components * migrating more components * made details components shared * move InlineCode component * moved InputText * moved Loading component * Moved Modal component * moved Select components * Moved Tooltip component * moved Search components * moved ColorMode provider * Moved Notification components and providers * used icons package * use UI colors in api-reference * moved Navbar component * used Navbar and Search in UI docs * added Feedback to UI docs * general enhancements * fix color mode * added copy colors file from ui-preset * added features and enhancements to UI docs * move Sidebar component and provider * general fixes and preparations for deployment * update docusaurus version * adjusted versions * fix output directory * remove rootDirectory property * fix yarn.lock * moved code component * added vale for all docs MD and MDX * fix tests * fix vale error * fix deployment errors * change ignore commands * add output directory * fix docs test * general fixes * content fixes * fix announcement script * added changeset * fix vale checks * added nofilter option * fix vale error
2.0 KiB
description, addHowToData
| description | addHowToData |
|---|---|
| In this document, you’ll learn about the local events module and how you can install it in your Medusa backend. | true |
Local Events Module
In this document, you’ll learn about the local events module and how you can install it in your Medusa backend.
Overview
Medusa’s modular architecture allows developers to extend or completely replace the logic used for events. You can create a custom module, or you can use the modules Medusa provides.
One of these modules is the local events module. This module allows you to utilize Node EventEmitter for the events system in Medusa. The Node EventEmitter is limited to a single process environment. This module is useful for development and testing, but it’s recommended to use the Redis events module in production.
This document will you guide you through installing the local events module.
Prerequisites
It’s assumed you already have a Medusa backend installed. If not, you can learn how to install it by following this guide.
Step 1: Install the Module
In the root directory of your Medusa backend, install the Redis events module with the following command:
npm install @medusajs/event-bus-local
Step 2: Add Configuration
In medusa-config.js, add the following to the exported object:
module.exports = {
// ...
modules: {
// ...
eventBus: {
resolve: "@medusajs/event-bus-local",
},
},
}
This registers the local events module as the main events service to use. This module does not require any options.
Step 4: Test Module
To test the module, run the following command to start the Medusa backend:
npx medusa develop
If the module was installed successfully, you should see the following message in the logs:
Local Event Bus installed. This is not recommended for production.