customer-registration 0.0.20 → 0.0.22

package/.medusa/server/src/admin/index.js

@@ -1,5 +1,4 @@
 "use strict";
-const i18nTranslations0 = {};
 const widgetModule = { widgets: [] };
 const routeModule = {
   routes: []
@@ -11,7 +10,7 @@ const formModule = { customFields: {} };
 const displayModule = {
   displays: {}
 };
-const i18nModule = { resources: i18nTranslations0 };
+const i18nModule = { resources: {} };
 const plugin = {
   widgetModule,
   routeModule,

package/.medusa/server/src/admin/index.mjs

@@ -1,4 +1,3 @@
-const i18nTranslations0 = {};
 const widgetModule = { widgets: [] };
 const routeModule = {
   routes: []
@@ -10,7 +9,7 @@ const formModule = { customFields: {} };
 const displayModule = {
   displays: {}
 };
-const i18nModule = { resources: i18nTranslations0 };
+const i18nModule = { resources: {} };
 const plugin = {
   widgetModule,
   routeModule,

package/.medusa/server/src/api/store/customers/route.js

@@ -47,4 +47,4 @@ async function POST(req, res) {
         }
     }
 }
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoicm91dGUuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi8uLi8uLi8uLi9zcmMvYXBpL3N0b3JlL2N1c3RvbWVycy9yb3V0ZS50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQW1CQSxvQkE0REM7QUE3RUQscURBQW1EO0FBaUI1QyxLQUFLLFVBQVUsSUFBSSxDQUN4QixHQUFrQixFQUNsQixHQUFtQjtJQUVuQixNQUFNLHFCQUFxQixHQUFHLEdBQUcsQ0FBQyxLQUFLLENBQUMsT0FBTyxDQUFDLGVBQU8sQ0FBQyxRQUFRLENBQUMsQ0FBQTtJQUNqRSxNQUFNLElBQUksR0FBRyxHQUFHLENBQUMsSUFBaUMsQ0FBQTtJQUVsRCxJQUFJLENBQUM7UUFDSCwwQ0FBMEM7UUFDMUMsTUFBTSxFQUNKLEtBQUssRUFDTCxVQUFVLEVBQ1YsU0FBUyxFQUNULEtBQUssRUFDTCxZQUFZLEVBQ1osUUFBUSxFQUNSLGNBQWMsRUFBRSxzQkFBc0IsRUFDdEMsY0FBYyxFQUFFLHNCQUFzQixFQUN0QyxHQUFHLElBQUksRUFDUixHQUFHLElBQUksQ0FBQTtRQUVSLDREQUE0RDtRQUM1RCxNQUFNLFlBQVksR0FBOEI7WUFDOUMsR0FBRyxJQUFJO1lBQ1AsS0FBSztZQUNMLFVBQVU7WUFDVixTQUFTO1lBQ1QsS0FBSztZQUNMLFlBQVk7WUFDWixRQUFRLEVBQUUsUUFBUSxJQUFJLEVBQUU7WUFDeEIsY0FBYyxFQUFFLEtBQUs7WUFDckIsY0FBYyxFQUFFLEtBQUs7U0FDdEIsQ0FBQTtRQUVELHdEQUF3RDtRQUN4RCxtQ0FBbUM7UUFDbkMsTUFBTSxTQUFTLEdBQUcsTUFBTSxxQkFBcUIsQ0FBQyxlQUFlLENBQUMsQ0FBQyxZQUFZLENBQUMsQ0FBQyxDQUFBO1FBQzdFLE1BQU0sUUFBUSxHQUFHLFNBQVMsQ0FBQyxDQUFDLENBQUMsQ0FBQTtRQUU3QiwwQ0FBMEM7UUFDMUMsTUFBTSxlQUFlLEdBQUcsTUFBTSxxQkFBcUIsQ0FBQyxnQkFBZ0IsQ0FBQyxRQUFRLENBQUMsRUFBRSxDQUFDLENBQUE7UUFFakYsNkNBQTZDO1FBQzdDLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDO1lBQ25CLFFBQVEsRUFBRSxlQUFlO1NBQzFCLENBQUMsQ0FBQTtJQUNKLENBQUM7SUFBQyxPQUFPLEtBQVUsRUFBRSxDQUFDO1FBQ3BCLDhCQUE4QjtRQUM5QixJQUFJLEtBQUssQ0FBQyxPQUFPLEVBQUUsUUFBUSxDQUFDLGdCQUFnQixDQUFDLElBQUksS0FBSyxDQUFDLE9BQU8sRUFBRSxRQUFRLENBQUMsV0FBVyxDQUFDLEVBQUUsQ0FBQztZQUN0RixHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQztnQkFDbkIsT0FBTyxFQUFFLDJDQUEyQztnQkFDcEQsSUFBSSxFQUFFLGlCQUFpQjthQUN4QixDQUFDLENBQUE7UUFDSixDQUFDO2FBQU0sQ0FBQztZQUNOLEdBQUcsQ0FBQyxNQUFNLENBQUMsR0FBRyxDQUFDLENBQUMsSUFBSSxDQUFDO2dCQUNuQixPQUFPLEVBQUUsS0FBSyxDQUFDLE9BQU8sSUFBSSwyQkFBMkI7Z0JBQ3JELElBQUksRUFBRSxjQUFjO2FBQ3JCLENBQUMsQ0FBQTtRQUNKLENBQUM7SUFDSCxDQUFDO0FBQ0gsQ0FBQyJ9
+//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoicm91dGUuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi8uLi8uLi8uLi9zcmMvYXBpL3N0b3JlL2N1c3RvbWVycy9yb3V0ZS50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQW1CQSxvQkE0REM7QUE3RUQscURBQW1EO0FBaUI1QyxLQUFLLFVBQVUsSUFBSSxDQUN4QixHQUFrQixFQUNsQixHQUFtQjtJQUVuQixNQUFNLHFCQUFxQixHQUFHLEdBQUcsQ0FBQyxLQUFLLENBQUMsT0FBTyxDQUFDLGVBQU8sQ0FBQyxRQUFRLENBQUMsQ0FBQTtJQUNqRSxNQUFNLElBQUksR0FBRyxHQUFHLENBQUMsSUFBaUMsQ0FBQTtJQUVsRCxJQUFJLENBQUM7UUFDSCwwQ0FBMEM7UUFDMUMsTUFBTSxFQUNKLEtBQUssRUFDTCxVQUFVLEVBQ1YsU0FBUyxFQUNULEtBQUssRUFDTCxZQUFZLEVBQ1osUUFBUSxFQUNSLGNBQWMsRUFBRSxzQkFBc0IsRUFDdEMsY0FBYyxFQUFFLHNCQUFzQixFQUN0QyxHQUFHLElBQUksRUFDUixHQUFHLElBQUksQ0FBQTtRQUVSLDREQUE0RDtRQUM1RCxNQUFNLFlBQVksR0FBOEI7WUFDOUMsR0FBRyxJQUFJO1lBQ1AsS0FBSztZQUNMLFVBQVU7WUFDVixTQUFTO1lBQ1QsS0FBSztZQUNMLFlBQVk7WUFDWixRQUFRLEVBQUUsUUFBUSxJQUFJLEVBQUU7WUFDeEIsY0FBYyxFQUFFLEtBQUs7WUFDckIsY0FBYyxFQUFFLEtBQUs7U0FDdEIsQ0FBQTtRQUVELHdEQUF3RDtRQUN4RCxtQ0FBbUM7UUFDbkMsTUFBTSxTQUFTLEdBQUcsTUFBTSxxQkFBcUIsQ0FBQyxlQUFlLENBQUMsQ0FBQyxZQUFZLENBQUMsQ0FBQyxDQUFBO1FBQzdFLE1BQU0sUUFBUSxHQUFHLFNBQVMsQ0FBQyxDQUFDLENBQUMsQ0FBQTtRQUU3QiwwQ0FBMEM7UUFDMUMsTUFBTSxlQUFlLEdBQUcsTUFBTSxxQkFBcUIsQ0FBQyxnQkFBZ0IsQ0FBQyxRQUFRLENBQUMsRUFBRSxDQUE4QixDQUFBO1FBRTlHLDZDQUE2QztRQUM3QyxHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQztZQUNuQixRQUFRLEVBQUUsZUFBZTtTQUMxQixDQUFDLENBQUE7SUFDSixDQUFDO0lBQUMsT0FBTyxLQUFVLEVBQUUsQ0FBQztRQUNwQiw4QkFBOEI7UUFDOUIsSUFBSSxLQUFLLENBQUMsT0FBTyxFQUFFLFFBQVEsQ0FBQyxnQkFBZ0IsQ0FBQyxJQUFJLEtBQUssQ0FBQyxPQUFPLEVBQUUsUUFBUSxDQUFDLFdBQVcsQ0FBQyxFQUFFLENBQUM7WUFDdEYsR0FBRyxDQUFDLE1BQU0sQ0FBQyxHQUFHLENBQUMsQ0FBQyxJQUFJLENBQUM7Z0JBQ25CLE9BQU8sRUFBRSwyQ0FBMkM7Z0JBQ3BELElBQUksRUFBRSxpQkFBaUI7YUFDeEIsQ0FBQyxDQUFBO1FBQ0osQ0FBQzthQUFNLENBQUM7WUFDTixHQUFHLENBQUMsTUFBTSxDQUFDLEdBQUcsQ0FBQyxDQUFDLElBQUksQ0FBQztnQkFDbkIsT0FBTyxFQUFFLEtBQUssQ0FBQyxPQUFPLElBQUksMkJBQTJCO2dCQUNyRCxJQUFJLEVBQUUsY0FBYzthQUNyQixDQUFDLENBQUE7UUFDSixDQUFDO0lBQ0gsQ0FBQztBQUNILENBQUMifQ==

package/.medusa/server/src/modules/customer-registration/migrations/Migration20250118000000AddEmailVerifiedColumn.js

@@ -0,0 +1,21 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.Migration20250118000000 = void 0;
+const migrations_1 = require("@medusajs/framework/mikro-orm/migrations");
+const TABLE_NAME = "customer";
+const EMAIL_COLUMN = "email_verified";
+const PHONE_COLUMN = "phone_verified";
+class Migration20250118000000 extends migrations_1.Migration {
+    async up() {
+        this.addSql(`alter table "${TABLE_NAME}"
+      add column if not exists "${EMAIL_COLUMN}" boolean not null default false,
+      add column if not exists "${PHONE_COLUMN}" boolean not null default false;`);
+    }
+    async down() {
+        this.addSql(`alter table "${TABLE_NAME}"
+      drop column if exists "${EMAIL_COLUMN}",
+      drop column if exists "${PHONE_COLUMN}";`);
+    }
+}
+exports.Migration20250118000000 = Migration20250118000000;
+//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiTWlncmF0aW9uMjAyNTAxMTgwMDAwMDBBZGRFbWFpbFZlcmlmaWVkQ29sdW1uLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vLi4vLi4vLi4vLi4vc3JjL21vZHVsZXMvY3VzdG9tZXItcmVnaXN0cmF0aW9uL21pZ3JhdGlvbnMvTWlncmF0aW9uMjAyNTAxMTgwMDAwMDBBZGRFbWFpbFZlcmlmaWVkQ29sdW1uLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiI7OztBQUFBLHlFQUFvRTtBQUVwRSxNQUFNLFVBQVUsR0FBRyxVQUFVLENBQUE7QUFDN0IsTUFBTSxZQUFZLEdBQUcsZ0JBQWdCLENBQUE7QUFDckMsTUFBTSxZQUFZLEdBQUcsZ0JBQWdCLENBQUE7QUFFckMsTUFBYSx1QkFBd0IsU0FBUSxzQkFBUztJQUNwRCxLQUFLLENBQUMsRUFBRTtRQUNOLElBQUksQ0FBQyxNQUFNLENBQUMsZ0JBQWdCLFVBQVU7a0NBQ1IsWUFBWTtrQ0FDWixZQUFZLG1DQUFtQyxDQUFDLENBQUE7SUFDaEYsQ0FBQztJQUVELEtBQUssQ0FBQyxJQUFJO1FBQ1IsSUFBSSxDQUFDLE1BQU0sQ0FBQyxnQkFBZ0IsVUFBVTsrQkFDWCxZQUFZOytCQUNaLFlBQVksSUFBSSxDQUFDLENBQUE7SUFDOUMsQ0FBQztDQUNGO0FBWkQsMERBWUMifQ==

package/README.md

@@ -1,13 +1,14 @@
-# Medusa Plugin: Customer Email Verified Registration Override
+# Medusa Plugin: Customer Registration Guard
 
-A Medusa v2 plugin that overrides the customer registration endpoint to set `email_verified = false` by default.
+A lean Medusa v2 plugin that overrides the store customer registration endpoint and guarantees both `email_verified` and `phone_verified` start as `false`.
 
 ## Features
 
-- Overrides the `POST /store/customers` registration endpoint
-- Forces `email_verified = false` and `phone_verified = false` for every new customer – no direct DB mutation required
-- Emits a notification-driven welcome email every time a customer registers successfully
-- Maintains all existing customer registration functionality
+- Overrides `POST /store/customers` with a drop-in route handler.
+- Forces `email_verified = false` and `phone_verified = false` for every new customer, regardless of the request payload.
+- Ships a lightweight Medusa module (`customer-registration`) so the bundled Mikro-ORM migration automatically runs during `npx medusa db:migrate`.
+- Adds both verification columns if they’re missing, ensuring downstream logic can rely on them.
+- No custom modules, admin extensions, subscribers, or providers — just the pieces required for registration hardening.
 
 ## Installation
 
@@ -52,28 +53,21 @@ yarn dev
 
 ## Usage
 
-### Registration
+### Registration override
 
-When a customer registers via `POST /store/customers`, the plugin automatically forces `email_verified = false` before persisting the customer with the Customer Module. No raw SQL access is required.
-
-### Welcome email subscriber
-
-- A subscriber listening on `customer.created` collects the newly created customer(s) and calls the Notification Module to dispatch an email using the template ID stored in `CUSTOMER_REGISTRATION_WELCOME_TEMPLATE_ID` (defaults to `customer-registration-success`).
-- Configure the Notification Module in your Medusa project and ensure at least one provider handles the `email` channel for the template ID above.
-- The notification payload includes the customer's `email`, `first_name`, `last_name`, and `full_name`, so templates can be fully personalized.
+When a shopper registers via `POST /store/customers`, the plugin intercepts the request, normalizes the payload, and always persists `email_verified = false` and `phone_verified = false`. The rest of Medusa’s default behavior is preserved by deferring to the Customer Module service.
 
 ### Database migration
 
-- The plugin ships with a Mikro-ORM migration (`Migration20250118000000AddEmailVerifiedColumn`) that adds both `email_verified BOOLEAN NOT NULL DEFAULT FALSE` and `phone_verified BOOLEAN NOT NULL DEFAULT FALSE` columns to the core `customer` table.
-- After installing or updating the plugin, run `npx medusa db:migrate` (or the equivalent package manager command) in your Medusa project to apply the migration before handling registrations.
+- A module-scoped migration (`Migration20250118000000AddEmailVerifiedColumn`) lives under `src/modules/customer-registration/migrations`. Medusa automatically discovers it when the plugin is registered.
+- After installing or updating the plugin, run `npx medusa db:migrate` in your Medusa project so the columns exist before handling registrations.
 
 ## Requirements
 
 - Medusa v2.11.2 or higher
-- Customer table must have `email_verified` and `phone_verified` boolean columns (default: `false`)
-- Run the plugin-provided migration so the columns are created (`npx medusa db:migrate`)
-- Notification Module configured with at least one provider that supports the `email` channel
-- `CUSTOMER_REGISTRATION_WELCOME_TEMPLATE_ID` set in your `.env`/deployment (optional – falls back to `customer-registration-success`)
+- Customer table must have `email_verified` and `phone_verified` boolean columns (default: `false`) — the provided migration handles this.
+- Run `npx medusa db:migrate` after installation so the module migration is applied.
+- No additional providers, subscribers, or admin extensions are required.
 
 ## Development
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "customer-registration",
-  "version": "0.0.20",
-  "description": "Medusa plugin to override customer registration endpoint to set email_verified = false by default.",
+  "version": "0.0.22",
+  "description": "Medusa plugin that overrides store customer registration and enforces email/phone verification flags.",
   "author": "Medusa (https://medusajs.com)",
   "license": "MIT",
   "files": [
@@ -9,16 +9,9 @@
   ],
   "exports": {
     "./package.json": "./package.json",
-    "./workflows": "./.medusa/server/src/workflows/index.js",
     "./.medusa/server/src/modules/*": "./.medusa/server/src/modules/*/index.js",
     "./modules/*": "./.medusa/server/src/modules/*/index.js",
-    "./providers/*": "./.medusa/server/src/providers/*/index.js",
-    "./*": "./.medusa/server/src/*.js",
-    "./admin": {
-      "import": "./.medusa/server/src/admin/index.mjs",
-      "require": "./.medusa/server/src/admin/index.js",
-      "default": "./.medusa/server/src/admin/index.js"
-    }
+    "./*": "./.medusa/server/src/*.js"
   },
   "keywords": [
     "medusa",
@@ -30,37 +23,19 @@
   "scripts": {
     "build": "medusa plugin:build",
     "dev": "medusa plugin:develop",
-    "prepublishOnly": "medusa plugin:build",
-    "publish": "npx medusa plugin:publish"
+    "prepublishOnly": "medusa plugin:build"
   },
   "devDependencies": {
-    "@medusajs/admin-sdk": "2.11.2",
     "@medusajs/cli": "2.11.2",
     "@medusajs/framework": "2.11.2",
-    "@medusajs/icons": "2.11.2",
     "@medusajs/medusa": "2.11.2",
-    "@medusajs/test-utils": "2.11.2",
-    "@medusajs/ui": "4.0.25",
-    "@swc/core": "1.5.7",
-    "@types/node": "^20.0.0",
-    "@types/react": "^18.3.2",
-    "@types/react-dom": "^18.2.25",
-    "prop-types": "^15.8.1",
-    "react": "^18.2.0",
-    "react-dom": "^18.2.0",
     "ts-node": "^10.9.2",
-    "typescript": "^5.6.2",
-    "vite": "^5.2.11",
-    "yalc": "^1.0.0-pre.53"
+    "typescript": "^5.6.2"
   },
   "peerDependencies": {
-    "@medusajs/admin-sdk": "2.11.2",
     "@medusajs/cli": "2.11.2",
     "@medusajs/framework": "2.11.2",
-    "@medusajs/icons": "2.11.2",
-    "@medusajs/medusa": "2.11.2",
-    "@medusajs/test-utils": "2.11.2",
-    "@medusajs/ui": "4.0.25"
+    "@medusajs/medusa": "2.11.2"
   },
   "engines": {
     "node": ">=20"

package/.medusa/server/src/api/admin/plugin/route.js

@@ -1,7 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.GET = GET;
-async function GET(req, res) {
-    res.sendStatus(200);
-}
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoicm91dGUuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi8uLi8uLi8uLi9zcmMvYXBpL2FkbWluL3BsdWdpbi9yb3V0ZS50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUVBLGtCQUtDO0FBTE0sS0FBSyxVQUFVLEdBQUcsQ0FDdkIsR0FBa0IsRUFDbEIsR0FBbUI7SUFFbkIsR0FBRyxDQUFDLFVBQVUsQ0FBQyxHQUFHLENBQUMsQ0FBQztBQUN0QixDQUFDIn0=

package/.medusa/server/src/api/store/plugin/route.js

@@ -1,7 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.GET = GET;
-async function GET(req, res) {
-    res.sendStatus(200);
-}
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoicm91dGUuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi8uLi8uLi8uLi9zcmMvYXBpL3N0b3JlL3BsdWdpbi9yb3V0ZS50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOztBQUVBLGtCQUtDO0FBTE0sS0FBSyxVQUFVLEdBQUcsQ0FDdkIsR0FBa0IsRUFDbEIsR0FBbUI7SUFFbkIsR0FBRyxDQUFDLFVBQVUsQ0FBQyxHQUFHLENBQUMsQ0FBQztBQUN0QixDQUFDIn0=

package/.medusa/server/src/migrations/Migration20250118000000AddEmailVerifiedColumn.js

@@ -1,21 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Migration20250118000000 = void 0;
-const migrations_1 = require("@medusajs/framework/mikro-orm/migrations");
-const TABLE_NAME = "customer";
-const EMAIL_COLUMN = "email_verified";
-const PHONE_COLUMN = "phone_verified";
-class Migration20250118000000 extends migrations_1.Migration {
-    async up() {
-        this.addSql(`alter table "${TABLE_NAME}"
-        add column if not exists "${EMAIL_COLUMN}" boolean not null default false,
-        add column if not exists "${PHONE_COLUMN}" boolean not null default false;`);
-    }
-    async down() {
-        this.addSql(`alter table "${TABLE_NAME}"
-        drop column if exists "${EMAIL_COLUMN}",
-        drop column if exists "${PHONE_COLUMN}";`);
-    }
-}
-exports.Migration20250118000000 = Migration20250118000000;
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiTWlncmF0aW9uMjAyNTAxMTgwMDAwMDBBZGRFbWFpbFZlcmlmaWVkQ29sdW1uLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vLi4vLi4vc3JjL21pZ3JhdGlvbnMvTWlncmF0aW9uMjAyNTAxMTgwMDAwMDBBZGRFbWFpbFZlcmlmaWVkQ29sdW1uLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiI7OztBQUFBLHlFQUFvRTtBQUVwRSxNQUFNLFVBQVUsR0FBRyxVQUFVLENBQUE7QUFDN0IsTUFBTSxZQUFZLEdBQUcsZ0JBQWdCLENBQUE7QUFDckMsTUFBTSxZQUFZLEdBQUcsZ0JBQWdCLENBQUE7QUFFckMsTUFBYSx1QkFBd0IsU0FBUSxzQkFBUztJQUMzQyxLQUFLLENBQUMsRUFBRTtRQUNmLElBQUksQ0FBQyxNQUFNLENBQ1QsZ0JBQWdCLFVBQVU7b0NBQ0ksWUFBWTtvQ0FDWixZQUFZLG1DQUFtQyxDQUM5RSxDQUFBO0lBQ0gsQ0FBQztJQUVRLEtBQUssQ0FBQyxJQUFJO1FBQ2pCLElBQUksQ0FBQyxNQUFNLENBQ1QsZ0JBQWdCLFVBQVU7aUNBQ0MsWUFBWTtpQ0FDWixZQUFZLElBQUksQ0FDNUMsQ0FBQTtJQUNILENBQUM7Q0FDRjtBQWhCRCwwREFnQkMifQ==

package/.medusa/server/src/subscribers/customer-created.js

@@ -1,60 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.config = void 0;
-exports.default = handleCustomerCreated;
-const utils_1 = require("@medusajs/framework/utils");
-const WELCOME_TEMPLATE_ID = process.env.CUSTOMER_REGISTRATION_WELCOME_TEMPLATE_ID ||
-    "customer-registration-success";
-async function handleCustomerCreated({ event: { data }, container, }) {
-    const logger = container.hasRegistration(utils_1.ContainerRegistrationKeys.LOGGER)
-        ? container.resolve(utils_1.ContainerRegistrationKeys.LOGGER)
-        : null;
-    if (!Array.isArray(data) || !data.length) {
-        return;
-    }
-    const customerIds = data
-        .map((payload) => payload?.id)
-        .filter((id) => typeof id === "string" && !!id);
-    if (!customerIds.length) {
-        return;
-    }
-    try {
-        const customerModuleService = container.resolve(utils_1.Modules.CUSTOMER);
-        const customers = await customerModuleService.listCustomers({
-            id: customerIds,
-        });
-        if (!customers.length) {
-            return;
-        }
-        if (!container.hasRegistration(utils_1.Modules.NOTIFICATION)) {
-            logger?.warn?.("[customer-registration] Notification module is not configured. Skipping welcome email.");
-            return;
-        }
-        const notificationModuleService = container.resolve(utils_1.Modules.NOTIFICATION);
-        await notificationModuleService.createNotifications(customers.map((customer) => ({
-            to: customer.email,
-            channel: "email",
-            template: WELCOME_TEMPLATE_ID,
-            resource_id: customer.id,
-            resource_type: "customer",
-            receiver_id: customer.id,
-            trigger_type: "customer-registration",
-            data: {
-                email: customer.email,
-                first_name: customer.first_name,
-                last_name: customer.last_name,
-                full_name: [customer.first_name, customer.last_name]
-                    .filter(Boolean)
-                    .join(" ")
-                    .trim(),
-            },
-        })));
-    }
-    catch (error) {
-        logger?.error?.("[customer-registration] Failed to send welcome email", error);
-    }
-}
-exports.config = {
-    event: utils_1.CustomerWorkflowEvents.CREATED,
-};
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiY3VzdG9tZXItY3JlYXRlZC5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uLy4uLy4uL3NyYy9zdWJzY3JpYmVycy9jdXN0b21lci1jcmVhdGVkLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiI7OztBQW1CQSx3Q0FvRUM7QUFsRkQscURBSWtDO0FBTWxDLE1BQU0sbUJBQW1CLEdBQ3ZCLE9BQU8sQ0FBQyxHQUFHLENBQUMseUNBQXlDO0lBQ3JELCtCQUErQixDQUFBO0FBRWxCLEtBQUssVUFBVSxxQkFBcUIsQ0FBQyxFQUNsRCxLQUFLLEVBQUUsRUFBRSxJQUFJLEVBQUUsRUFDZixTQUFTLEdBQzhCO0lBQ3ZDLE1BQU0sTUFBTSxHQUFrQixTQUFTLENBQUMsZUFBZSxDQUNyRCxpQ0FBeUIsQ0FBQyxNQUFNLENBQ2pDO1FBQ0MsQ0FBQyxDQUFDLFNBQVMsQ0FBQyxPQUFPLENBQUMsaUNBQXlCLENBQUMsTUFBTSxDQUFDO1FBQ3JELENBQUMsQ0FBQyxJQUFJLENBQUE7SUFFUixJQUFJLENBQUMsS0FBSyxDQUFDLE9BQU8sQ0FBQyxJQUFJLENBQUMsSUFBSSxDQUFDLElBQUksQ0FBQyxNQUFNLEVBQUUsQ0FBQztRQUN6QyxPQUFNO0lBQ1IsQ0FBQztJQUVELE1BQU0sV0FBVyxHQUFHLElBQUk7U0FDckIsR0FBRyxDQUFDLENBQUMsT0FBTyxFQUFFLEVBQUUsQ0FBQyxPQUFPLEVBQUUsRUFBRSxDQUFDO1NBQzdCLE1BQU0sQ0FBQyxDQUFDLEVBQUUsRUFBZ0IsRUFBRSxDQUFDLE9BQU8sRUFBRSxLQUFLLFFBQVEsSUFBSSxDQUFDLENBQUMsRUFBRSxDQUFDLENBQUE7SUFFL0QsSUFBSSxDQUFDLFdBQVcsQ0FBQyxNQUFNLEVBQUUsQ0FBQztRQUN4QixPQUFNO0lBQ1IsQ0FBQztJQUVELElBQUksQ0FBQztRQUNILE1BQU0scUJBQXFCLEdBQUcsU0FBUyxDQUFDLE9BQU8sQ0FBQyxlQUFPLENBQUMsUUFBUSxDQUFDLENBQUE7UUFFakUsTUFBTSxTQUFTLEdBQUcsTUFBTSxxQkFBcUIsQ0FBQyxhQUFhLENBQUM7WUFDMUQsRUFBRSxFQUFFLFdBQVc7U0FDaEIsQ0FBQyxDQUFBO1FBRUYsSUFBSSxDQUFDLFNBQVMsQ0FBQyxNQUFNLEVBQUUsQ0FBQztZQUN0QixPQUFNO1FBQ1IsQ0FBQztRQUVELElBQUksQ0FBQyxTQUFTLENBQUMsZUFBZSxDQUFDLGVBQU8sQ0FBQyxZQUFZLENBQUMsRUFBRSxDQUFDO1lBQ3JELE1BQU0sRUFBRSxJQUFJLEVBQUUsQ0FDWix3RkFBd0YsQ0FDekYsQ0FBQTtZQUNELE9BQU07UUFDUixDQUFDO1FBRUQsTUFBTSx5QkFBeUIsR0FBRyxTQUFTLENBQUMsT0FBTyxDQUFDLGVBQU8sQ0FBQyxZQUFZLENBQUMsQ0FBQTtRQUV6RSxNQUFNLHlCQUF5QixDQUFDLG1CQUFtQixDQUNqRCxTQUFTLENBQUMsR0FBRyxDQUFDLENBQUMsUUFBUSxFQUFFLEVBQUUsQ0FBQyxDQUFDO1lBQzNCLEVBQUUsRUFBRSxRQUFRLENBQUMsS0FBSztZQUNsQixPQUFPLEVBQUUsT0FBTztZQUNoQixRQUFRLEVBQUUsbUJBQW1CO1lBQzdCLFdBQVcsRUFBRSxRQUFRLENBQUMsRUFBRTtZQUN4QixhQUFhLEVBQUUsVUFBVTtZQUN6QixXQUFXLEVBQUUsUUFBUSxDQUFDLEVBQUU7WUFDeEIsWUFBWSxFQUFFLHVCQUF1QjtZQUNyQyxJQUFJLEVBQUU7Z0JBQ0osS0FBSyxFQUFFLFFBQVEsQ0FBQyxLQUFLO2dCQUNyQixVQUFVLEVBQUUsUUFBUSxDQUFDLFVBQVU7Z0JBQy9CLFNBQVMsRUFBRSxRQUFRLENBQUMsU0FBUztnQkFDN0IsU0FBUyxFQUFFLENBQUMsUUFBUSxDQUFDLFVBQVUsRUFBRSxRQUFRLENBQUMsU0FBUyxDQUFDO3FCQUNqRCxNQUFNLENBQUMsT0FBTyxDQUFDO3FCQUNmLElBQUksQ0FBQyxHQUFHLENBQUM7cUJBQ1QsSUFBSSxFQUFFO2FBQ1Y7U0FDRixDQUFDLENBQUMsQ0FDSixDQUFBO0lBQ0gsQ0FBQztJQUFDLE9BQU8sS0FBSyxFQUFFLENBQUM7UUFDZixNQUFNLEVBQUUsS0FBSyxFQUFFLENBQ2Isc0RBQXNELEVBQ3RELEtBQUssQ0FDTixDQUFBO0lBQ0gsQ0FBQztBQUNILENBQUM7QUFFWSxRQUFBLE1BQU0sR0FBcUI7SUFDdEMsS0FBSyxFQUFFLDhCQUFzQixDQUFDLE9BQU87Q0FDdEMsQ0FBQSJ9

package/src/admin/README.md

@@ -1,31 +0,0 @@
-# Admin Customizations
-
-You can extend the Medusa Admin to add widgets and new pages. Your customizations interact with API routes to provide merchants with custom functionalities.
-
-## Example: Create a Widget
-
-A widget is a React component that can be injected into an existing page in the admin dashboard.
-
-For example, create the file `src/admin/widgets/product-widget.tsx` with the following content:
-
-```tsx title="src/admin/widgets/product-widget.tsx"
-import { defineWidgetConfig } from "@medusajs/admin-sdk"
-
-// The widget
-const ProductWidget = () => {
-  return (
-    <div>
-      <h2>Product Widget</h2>
-    </div>
-  )
-}
-
-// The widget's configurations
-export const config = defineWidgetConfig({
-  zone: "product.details.after",
-})
-
-export default ProductWidget
-```
-
-This inserts a widget with the text “Product Widget” at the end of a product’s details page.

package/src/admin/i18n/README.md

@@ -1,58 +0,0 @@
-# Admin Customizations Translations
-
-The Medusa Admin dashboard supports multiple languages for its interface. Medusa uses [react-i18next](https://react.i18next.com/) to manage translations in the admin dashboard.
-
-To add translations, create JSON translation files for each language under the `src/admin/i18n/json` directory. For example, create the `src/admin/i18n/json/en.json` file with the following content:
-
-```json
-{
-  "brands": {
-    "title": "Brands",
-    "description": "Manage your product brands"
-  },
-  "done": "Done"
-}
-```
-
-Then, export the translations in `src/admin/i18n/index.ts`:
-
-```ts
-import en from "./json/en.json" with { type: "json" }
-
-export default {
-  en: {
-    translation: en,
-  },
-}
-```
-
-Finally, use translations in your admin widgets and routes using the `useTranslation` hook:
-
-```tsx
-import { defineWidgetConfig } from "@medusajs/admin-sdk"
-import { Button, Container, Heading } from "@medusajs/ui"
-import { useTranslation } from "react-i18next"
-
-const ProductWidget = () => {
-  const { t } = useTranslation()
-  return (
-    <Container className="p-0">
-      <div className="flex items-center justify-between px-6 py-4">
-        <Heading level="h2">{t("brands.title")}</Heading>
-        <p>{t("brands.description")}</p>
-      </div>
-      <div className="flex justify-end px-6 py-4">
-        <Button variant="primary">{t("done")}</Button>
-      </div>
-    </Container>
-  )
-}
-
-export const config = defineWidgetConfig({
-  zone: "product.details.before",
-})
-
-export default ProductWidget
-```
-
-Learn more about translating admin extensions in the [Translate Admin Customizations](https://docs.medusajs.com/learn/fundamentals/admin/translations) documentation.

package/src/admin/i18n/index.ts

@@ -1 +0,0 @@
-export default {}

package/src/admin/tsconfig.json

@@ -1,24 +0,0 @@
-{
-  "compilerOptions": {
-    "target": "ES2020",
-    "useDefineForClassFields": true,
-    "lib": ["ES2020", "DOM", "DOM.Iterable"],
-    "module": "ESNext",
-    "skipLibCheck": true,
-
-    /* Bundler mode */
-    "moduleResolution": "bundler",
-    "allowImportingTsExtensions": true,
-    "resolveJsonModule": true,
-    "isolatedModules": true,
-    "noEmit": true,
-    "jsx": "react-jsx",
-
-    /* Linting */
-    "strict": true,
-    "noUnusedLocals": true,
-    "noUnusedParameters": true,
-    "noFallthroughCasesInSwitch": true
-  },
-  "include": ["."]
-}

package/src/admin/vite-env.d.ts

@@ -1 +0,0 @@
-/// <reference types="vite/client" />

package/src/api/README.md

@@ -1,133 +0,0 @@
-# Custom API Routes
-
-An API Route is a REST API endpoint.
-
-An API Route is created in a TypeScript or JavaScript file under the `/src/api` directory of your Medusa application. The file’s name must be `route.ts` or `route.js`.
-
-For example, to create a `GET` API Route at `/store/hello-world`, create the file `src/api/store/hello-world/route.ts` with the following content:
-
-```ts
-import type { MedusaRequest, MedusaResponse } from "@medusajs/framework/http";
-
-export async function GET(req: MedusaRequest, res: MedusaResponse) {
-  res.json({
-    message: "Hello world!",
-  });
-}
-```
-
-## Supported HTTP methods
-
-The file based routing supports the following HTTP methods:
-
-- GET
-- POST
-- PUT
-- PATCH
-- DELETE
-- OPTIONS
-- HEAD
-
-You can define a handler for each of these methods by exporting a function with the name of the method in the paths `route.ts` file.
-
-For example:
-
-```ts
-import type { MedusaRequest, MedusaResponse } from "@medusajs/framework/http";
-
-export async function GET(req: MedusaRequest, res: MedusaResponse) {
-  // Handle GET requests
-}
-
-export async function POST(req: MedusaRequest, res: MedusaResponse) {
-  // Handle POST requests
-}
-
-export async function PUT(req: MedusaRequest, res: MedusaResponse) {
-  // Handle PUT requests
-}
-```
-
-## Parameters
-
-To create an API route that accepts a path parameter, create a directory within the route's path whose name is of the format `[param]`.
-
-For example, if you want to define a route that takes a `productId` parameter, you can do so by creating a file called `/api/products/[productId]/route.ts`:
-
-```ts
-import type {
-  MedusaRequest,
-  MedusaResponse,
-} from "@medusajs/framework/http"
-
-export async function GET(req: MedusaRequest, res: MedusaResponse) {
-  const { productId } = req.params;
-
-  res.json({
-    message: `You're looking for product ${productId}`
-  })
-}
-```
-
-To create an API route that accepts multiple path parameters, create within the file's path multiple directories whose names are of the format `[param]`.
-
-For example, if you want to define a route that takes both a `productId` and a `variantId` parameter, you can do so by creating a file called `/api/products/[productId]/variants/[variantId]/route.ts`.
-
-## Using the container
-
-The Medusa container is available on `req.scope`. Use it to access modules' main services and other registered resources:
-
-```ts
-import type {
-  MedusaRequest,
-  MedusaResponse,
-} from "@medusajs/framework/http"
-
-export const GET = async (
-  req: MedusaRequest,
-  res: MedusaResponse
-) => {
-  const productModuleService = req.scope.resolve("product")
-
-  const [, count] = await productModuleService.listAndCount()
-
-  res.json({
-    count,
-  })
-}
-```
-
-## Middleware
-
-You can apply middleware to your routes by creating a file called `/api/middlewares.ts`. This file must export a configuration object with what middleware you want to apply to which routes.
-
-For example, if you want to apply a custom middleware function to the `/store/custom` route, you can do so by adding the following to your `/api/middlewares.ts` file:
-
-```ts
-import { defineMiddlewares } from "@medusajs/framework/http"
-import type {
-  MedusaRequest,
-  MedusaResponse,
-  MedusaNextFunction,
-} from "@medusajs/framework/http";
-
-async function logger(
-  req: MedusaRequest,
-  res: MedusaResponse,
-  next: MedusaNextFunction
-) {
-  console.log("Request received");
-  next();
-}
-
-export default defineMiddlewares({
-  routes: [
-    {
-      matcher: "/store/custom",
-      middlewares: [logger],
-    },
-  ],
-})
-```
-
-The `matcher` property can be either a string or a regular expression. The `middlewares` property accepts an array of middleware functions.

package/src/api/admin/plugin/route.ts

@@ -1,8 +0,0 @@
-import { MedusaRequest, MedusaResponse } from "@medusajs/framework/http";
-
-export async function GET(
-  req: MedusaRequest,
-  res: MedusaResponse
-) {
-  res.sendStatus(200);
-}

package/src/api/store/customers/route.ts

@@ -1,81 +0,0 @@
-import type { CreateCustomerDTO } from "@medusajs/framework/types"
-import { MedusaRequest, MedusaResponse } from "@medusajs/framework/http"
-import { Modules } from "@medusajs/framework/utils"
-
-/**
- * Override the store customer registration route
- * This route handles POST /store/customers
- * Based on: https://docs.medusajs.com/resources/storefront-development/customers/register
- * 
- * Forces email_verified = false and phone_verified = false on all new customer registrations
- */
-
-
-type CreateCustomerExtendedDTO = Partial<CreateCustomerDTO> & {
-  email_verified?: boolean
-  phone_verified?: boolean
-}
-
-
-export async function POST(
-  req: MedusaRequest,
-  res: MedusaResponse
-) {
-  const customerModuleService = req.scope.resolve(Modules.CUSTOMER)
-  const body = req.body as CreateCustomerExtendedDTO
-
-  try {
-    // Extract customer data from request body
-    const {
-      email,
-      first_name,
-      last_name,
-      phone,
-      company_name,
-      metadata,
-      email_verified: _incomingEmailVerified,
-      phone_verified: _incomingPhoneVerified,
-      ...rest
-    } = body
-
-    // Prepare customer data with verified flags forced to false
-    const customerData: CreateCustomerExtendedDTO = {
-      ...rest,
-      email,
-      first_name,
-      last_name,
-      phone,
-      company_name,
-      metadata: metadata ?? {},
-      email_verified: false,
-      phone_verified: false,
-    }
-
-    // Create the customer using the customer module service
-    // createCustomers expects an array
-    const customers = await customerModuleService.createCustomers([customerData])
-    const customer = customers[0]
-
-    // Retrieve the created customer to return
-    const createdCustomer = await customerModuleService.retrieveCustomer(customer.id)
-
-    // Return the customer in the expected format
-    res.status(201).json({
-      customer: createdCustomer,
-    })
-  } catch (error: any) {
-    // Handle errors appropriately
-    if (error.message?.includes("already exists") || error.message?.includes("duplicate")) {
-      res.status(409).json({
-        message: "A customer with this email already exists",
-        type: "duplicate_error",
-      })
-    } else {
-      res.status(400).json({
-        message: error.message || "Failed to create customer",
-        type: "invalid_data",
-      })
-    }
-  }
-}
-

package/src/api/store/plugin/route.ts

@@ -1,8 +0,0 @@
-import { MedusaRequest, MedusaResponse } from "@medusajs/framework/http";
-
-export async function GET(
-  req: MedusaRequest,
-  res: MedusaResponse
-) {
-  res.sendStatus(200);
-}

package/src/jobs/README.md

@@ -1,36 +0,0 @@
-# Custom scheduled jobs
-
-A scheduled job is a function executed at a specified interval of time in the background of your Medusa application.
-
-A scheduled job is created in a TypeScript or JavaScript file under the `src/jobs` directory.
-
-For example, create the file `src/jobs/hello-world.ts` with the following content:
-
-```ts
-import {
-  MedusaContainer
-} from "@medusajs/framework/types";
-
-export default async function myCustomJob(container: MedusaContainer) {
-  const productService = container.resolve("product")
-
-  const products = await productService.listAndCountProducts();
-
-  // Do something with the products
-}
-
-export const config = {
-  name: "daily-product-report",
-  schedule: "0 0 * * *", // Every day at midnight
-};
-```
-
-A scheduled job file must export:
-
-- The function to be executed whenever it’s time to run the scheduled job.
-- A configuration object defining the job. It has three properties:
-  - `name`: a unique name for the job.
-  - `schedule`: a [cron expression](https://crontab.guru/).
-  - `numberOfExecutions`: an optional integer, specifying how many times the job will execute before being removed
-
-The `handler` is a function that accepts one parameter, `container`, which is a `MedusaContainer` instance used to resolve services.

package/src/links/README.md

@@ -1,26 +0,0 @@
-# Module Links
-
-A module link forms an association between two data models of different modules, while maintaining module isolation.
-
-Learn more about links in [this documentation](https://docs.medusajs.com/learn/fundamentals/module-links)
-
-For example:
-
-```ts
-import BlogModule from "../modules/blog"
-import ProductModule from "@medusajs/medusa/product"
-import { defineLink } from "@medusajs/framework/utils"
-
-export default defineLink(
-  ProductModule.linkable.product,
-  BlogModule.linkable.post
-)
-```
-
-This defines a link between the Product Module's `product` data model and the Blog Module (custom module)'s `post` data model.
-
-Then, in the Medusa application using this plugin, run the following command to sync the links to the database:
-
-```bash
-npx medusa db:migrate
-```

package/src/migrations/Migration20250118000000AddEmailVerifiedColumn.ts

@@ -1,24 +0,0 @@
-import { Migration } from "@medusajs/framework/mikro-orm/migrations"
-
-const TABLE_NAME = "customer"
-const EMAIL_COLUMN = "email_verified"
-const PHONE_COLUMN = "phone_verified"
-
-export class Migration20250118000000 extends Migration {
-  override async up(): Promise<void> {
-    this.addSql(
-      `alter table "${TABLE_NAME}"
-        add column if not exists "${EMAIL_COLUMN}" boolean not null default false,
-        add column if not exists "${PHONE_COLUMN}" boolean not null default false;`
-    )
-  }
-
-  override async down(): Promise<void> {
-    this.addSql(
-      `alter table "${TABLE_NAME}"
-        drop column if exists "${EMAIL_COLUMN}",
-        drop column if exists "${PHONE_COLUMN}";`
-    )
-  }
-}
-

package/src/modules/README.md

@@ -1,116 +0,0 @@
-# Custom Module
-
-A module is a package of reusable functionalities. It can be integrated into your Medusa application without affecting the overall system. You can create a module as part of a plugin.
-
-Learn more about modules in [this documentation](https://docs.medusajs.com/learn/fundamentals/modules).
-
-To create a module:
-
-## 1. Create a Data Model
-
-A data model represents a table in the database. You create a data model in a TypeScript or JavaScript file under the `models` directory of a module.
-
-For example, create the file `src/modules/blog/models/post.ts` with the following content:
-
-```ts
-import { model } from "@medusajs/framework/utils"
-
-const Post = model.define("post", {
-  id: model.id().primaryKey(),
-  title: model.text(),
-})
-
-export default Post
-```
-
-## 2. Create a Service
-
-A module must define a service. A service is a TypeScript or JavaScript class holding methods related to a business logic or commerce functionality.
-
-For example, create the file `src/modules/blog/service.ts` with the following content:
-
-```ts
-import { MedusaService } from "@medusajs/framework/utils"
-import Post from "./models/post"
-
-class BlogModuleService extends MedusaService({
-  Post,
-}){
-}
-
-export default BlogModuleService
-```
-
-## 3. Export Module Definition
-
-A module must have an `index.ts` file in its root directory that exports its definition. The definition specifies the main service of the module.
-
-For example, create the file `src/modules/blog/index.ts` with the following content:
-
-```ts
-import BlogModuleService from "./service"
-import { Module } from "@medusajs/framework/utils"
-
-export const BLOG_MODULE = "blog"
-
-export default Module(BLOG_MODULE, {
-  service: BlogModuleService,
-})
-```
-
-## 4. Generate Migrations
-
-To generate migrations for your module, run the following command in the plugin's directory:
-
-```bash
-npx medusa plugin:db:genreate
-```
-
-## Use Module
-
-You can use the module in customizations within the plugin or within the Medusa application using this plugin. When the plugin is added to a Medusa application, all its modules are registered as well.
-
-For example, to use the module in an API route:
-
-```ts
-import { MedusaRequest, MedusaResponse } from "@medusajs/framework"
-import BlogModuleService from "../../../modules/blog/service"
-import { BLOG_MODULE } from "../../../modules/blog"
-
-export async function GET(
-  req: MedusaRequest,
-  res: MedusaResponse
-): Promise<void> {
-  const blogModuleService: BlogModuleService = req.scope.resolve(
-    BLOG_MODULE
-  )
-
-  const posts = await blogModuleService.listPosts()
-
-  res.json({
-    posts
-  })
-}
-```
-
-## Module Options
-
-When you register the plugin in the Medusa application, it can accept options. These options are passed to the modules within the plugin:
-
-```ts
-import { defineConfig } from "@medusajs/framework/utils"
-
-module.exports = defineConfig({
-  // ...
-  plugins: [
-    {
-      resolve: "@myorg/plugin-name",
-      options: {
-        apiKey: process.env.API_KEY,
-      },
-    },
-  ],
-})
-```
-
-Learn more about module options in [this documentation](https://docs.medusajs.com/learn/fundamentals/modules/options).

package/src/providers/README.md

@@ -1,30 +0,0 @@
-## Module Providers
-
-You can create module providers, such as Notification or File Module Providers under a sub-directory of this directory. For example, `src/providers/my-notification`.
-
-Then, you register them in the Medusa application as `plugin-name/providers/my-notification`:
-
-```ts
-module.exports = defineConfig({
-  // ...
-  modules: [
-    {
-      resolve: "@medusajs/medusa/notification",
-      options: {
-        providers: [
-          {
-            resolve: "@myorg/plugin-name/providers/my-notification",
-            id: "my-notification",
-            options: {
-              channels: ["email"],
-              // provider options...
-            },
-          },
-        ],
-      },
-    },
-  ],
-})
-```
-
-Learn more in [this documentation](https://docs.medusajs.com/learn/fundamentals/plugins/create).

package/src/subscribers/README.md

@@ -1,59 +0,0 @@
-# Custom subscribers
-
-Subscribers handle events emitted in the Medusa application.
-
-The subscriber is created in a TypeScript or JavaScript file under the `src/subscribers` directory.
-
-For example, create the file `src/subscribers/product-created.ts` with the following content:
-
-```ts
-import {
-  type SubscriberConfig,
-} from "@medusajs/framework"
-
-// subscriber function
-export default async function productCreateHandler() {
-  console.log("A product was created")
-}
-
-// subscriber config
-export const config: SubscriberConfig = {
-  event: "product.created",
-}
-```
-
-A subscriber file must export:
-
-- The subscriber function that is an asynchronous function executed whenever the associated event is triggered.
-- A configuration object defining the event this subscriber is listening to.
-
-## Subscriber Parameters
-
-A subscriber receives an object having the following properties:
-
-- `event`: An object holding the event's details. It has a `data` property, which is the event's data payload.
-- `container`: The Medusa container. Use it to resolve modules' main services and other registered resources.
-
-```ts
-import type {
-  SubscriberArgs,
-  SubscriberConfig,
-} from "@medusajs/framework"
-
-export default async function productCreateHandler({
-  event: { data },
-  container,
-}: SubscriberArgs<{ id: string }>) {
-  const productId = data.id
-
-  const productModuleService = container.resolve("product")
-
-  const product = await productModuleService.retrieveProduct(productId)
-
-  console.log(`The product ${product.title} was created`)
-}
-
-export const config: SubscriberConfig = {
-  event: "product.created",
-}
-```

package/src/subscribers/customer-created.ts

@@ -1,93 +0,0 @@
-import type { Logger } from "@medusajs/framework/types"
-import type {
-  SubscriberArgs,
-  SubscriberConfig,
-} from "@medusajs/framework/subscribers"
-import {
-  ContainerRegistrationKeys,
-  CustomerWorkflowEvents,
-  Modules,
-} from "@medusajs/framework/utils"
-
-type CustomerCreatedPayload = Array<{
-  id: string
-}>
-
-const WELCOME_TEMPLATE_ID =
-  process.env.CUSTOMER_REGISTRATION_WELCOME_TEMPLATE_ID ||
-  "customer-registration-success"
-
-export default async function handleCustomerCreated({
-  event: { data },
-  container,
-}: SubscriberArgs<CustomerCreatedPayload>) {
-  const logger: Logger | null = container.hasRegistration(
-    ContainerRegistrationKeys.LOGGER
-  )
-    ? container.resolve(ContainerRegistrationKeys.LOGGER)
-    : null
-
-  if (!Array.isArray(data) || !data.length) {
-    return
-  }
-
-  const customerIds = data
-    .map((payload) => payload?.id)
-    .filter((id): id is string => typeof id === "string" && !!id)
-
-  if (!customerIds.length) {
-    return
-  }
-
-  try {
-    const customerModuleService = container.resolve(Modules.CUSTOMER)
-
-    const customers = await customerModuleService.listCustomers({
-      id: customerIds,
-    })
-
-    if (!customers.length) {
-      return
-    }
-
-    if (!container.hasRegistration(Modules.NOTIFICATION)) {
-      logger?.warn?.(
-        "[customer-registration] Notification module is not configured. Skipping welcome email."
-      )
-      return
-    }
-
-    const notificationModuleService = container.resolve(Modules.NOTIFICATION)
-
-    await notificationModuleService.createNotifications(
-      customers.map((customer) => ({
-        to: customer.email,
-        channel: "email",
-        template: WELCOME_TEMPLATE_ID,
-        resource_id: customer.id,
-        resource_type: "customer",
-        receiver_id: customer.id,
-        trigger_type: "customer-registration",
-        data: {
-          email: customer.email,
-          first_name: customer.first_name,
-          last_name: customer.last_name,
-          full_name: [customer.first_name, customer.last_name]
-            .filter(Boolean)
-            .join(" ")
-            .trim(),
-        },
-      }))
-    )
-  } catch (error) {
-    logger?.error?.(
-      "[customer-registration] Failed to send welcome email",
-      error
-    )
-  }
-}
-
-export const config: SubscriberConfig = {
-  event: CustomerWorkflowEvents.CREATED,
-}
-

package/src/workflows/README.md

@@ -1,79 +0,0 @@
-# Custom Workflows
-
-A workflow is a series of queries and actions that complete a task.
-
-The workflow is created in a TypeScript or JavaScript file under the `src/workflows` directory.
-
-For example:
-
-```ts
-import {
-  createStep,
-  createWorkflow,
-  WorkflowResponse,
-  StepResponse,
-} from "@medusajs/framework/workflows-sdk"
-
-const step1 = createStep("step-1", async () => {
-  return new StepResponse(`Hello from step one!`)
-})
-
-type WorkflowInput = {
-  name: string
-}
-
-const step2 = createStep(
-  "step-2",
-  async ({ name }: WorkflowInput) => {
-    return new StepResponse(`Hello ${name} from step two!`)
-  }
-)
-
-type WorkflowOutput = {
-  message1: string
-  message2: string
-}
-
-const helloWorldWorkflow = createWorkflow(
-  "hello-world",
-  (input: WorkflowInput) => {
-    const greeting1 = step1()
-    const greeting2 = step2(input)
-    
-    return new WorkflowResponse({
-      message1: greeting1,
-      message2: greeting2
-    })
-  }
-)
-
-export default helloWorldWorkflow
-```
-
-## Execute Workflow
-
-You can execute the workflow from other resources, such as API routes, scheduled jobs, or subscribers.
-
-For example, to execute the workflow in an API route:
-
-```ts
-import type {
-  MedusaRequest,
-  MedusaResponse,
-} from "@medusajs/framework"
-import myWorkflow from "../../../workflows/hello-world"
-
-export async function GET(
-  req: MedusaRequest,
-  res: MedusaResponse
-) {
-  const { result } = await myWorkflow(req.scope)
-    .run({
-      input: {
-        name: req.query.name as string,
-      },
-    })
-
-  res.send(result)
-}
-```