motia 0.8.5-beta.142 → 0.8.5-beta.143-445618

package/dist/cjs/constants.js

@@ -1,6 +1,11 @@
 "use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.isTutorialDisabled = exports.workbenchBase = void 0;
+const node_fs_1 = __importDefault(require("node:fs"));
+const node_path_1 = __importDefault(require("node:path"));
 function getWorkbenchBase() {
     const basePath = process.env.MOTIA_WORKBENCH_BASE;
     if (basePath === '/') {
@@ -9,4 +14,4 @@ function getWorkbenchBase() {
     return basePath && basePath[0] !== '/' ? `/${basePath}` : basePath || '';
 }
 exports.workbenchBase = getWorkbenchBase();
-exports.isTutorialDisabled = process.env.MOTIA_TUTORIAL_DISABLED === 'true';
+exports.isTutorialDisabled = process.env.MOTIA_TUTORIAL_DISABLED === 'true' || !node_fs_1.default.existsSync(node_path_1.default.join(process.cwd(), 'tutorial/tutorial.tsx'));

package/dist/esm/constants.js

@@ -1,3 +1,5 @@
+import fs from 'node:fs';
+import path from 'node:path';
 function getWorkbenchBase() {
     const basePath = process.env.MOTIA_WORKBENCH_BASE;
     if (basePath === '/') {
@@ -6,4 +8,4 @@ function getWorkbenchBase() {
     return basePath && basePath[0] !== '/' ? `/${basePath}` : basePath || '';
 }
 export const workbenchBase = getWorkbenchBase();
-export const isTutorialDisabled = process.env.MOTIA_TUTORIAL_DISABLED === 'true';
+export const isTutorialDisabled = process.env.MOTIA_TUTORIAL_DISABLED === 'true' || !fs.existsSync(path.join(process.cwd(), 'tutorial/tutorial.tsx'));

package/dist/esm/create/templates/python/tutorial/api_step.py-features.json.txt

@@ -0,0 +1,69 @@
+[
+  {
+    "id": "step-configuration",
+    "title": "Step Configuration",
+    "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
+    "lines": [
+      "6-30"
+    ]
+  },
+  {
+    "id": "api-configuration",
+    "title": "API Step",
+    "description": "Definition of an API endpoint",
+    "lines": [
+      "23-24"
+    ]
+  },
+  {
+    "id": "request-body",
+    "title": "Request body",
+    "description": "Definition of the expected request body. Motia will automatically generate types based on this schema.",
+    "lines": [
+      "6-16",
+      "25"
+    ]
+  },
+  {
+    "id": "response-payload",
+    "title": "Response Payload",
+    "description": "Definition of the expected response payload, Motia will generate the types automatically based on this schema. This is also important to create the Open API spec later.",
+    "lines": [
+      "4",
+      "26-28"
+    ]
+  },
+  {
+    "id": "event-driven-architecture",
+    "title": "Emits",
+    "description": "We can define the events that this step will emit, this is how we can trigger other Motia Steps.",
+    "lines": [
+      "29",
+      "42-50"
+    ]
+  },
+  {
+    "id": "handler",
+    "title": "Handler",
+    "description": "The handler is the function that will be executed when the step is triggered. This one receives the request body and emits events.",
+    "lines": [
+      "32-52"
+    ]
+  },
+  {
+    "id": "logger",
+    "title": "Logger",
+    "description": "The logger is a utility that allows you to log messages to the console. It is available in the handler function. We encourage you to use it instead of console.log. It will automatically be tied to the trace id of the request.",
+    "lines": [
+      "34"
+    ]
+  },
+  {
+    "id": "http-response",
+    "title": "HTTP Response",
+    "description": "The handler can return a response to the client. This is how we can return a response to the client. It must comply with the responseSchema defined in the step configuration.",
+    "lines": [
+      "52"
+    ]
+  }
+]

package/dist/esm/create/templates/python/tutorial/petstore/api_step.py-features.json.txt

@@ -0,0 +1,69 @@
+[
+  {
+    "id": "step-configuration",
+    "title": "Step Configuration",
+    "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
+    "lines": [
+      "6-30"
+    ]
+  },
+  {
+    "id": "api-configuration",
+    "title": "API Step",
+    "description": "Definition of an API endpoint",
+    "lines": [
+      "23-24"
+    ]
+  },
+  {
+    "id": "request-body",
+    "title": "Request body",
+    "description": "Definition of the expected request body. Motia will automatically generate types based on this schema.",
+    "lines": [
+      "6-16",
+      "25"
+    ]
+  },
+  {
+    "id": "response-payload",
+    "title": "Response Payload",
+    "description": "Definition of the expected response payload, Motia will generate the types automatically based on this schema. This is also important to create the Open API spec later.",
+    "lines": [
+      "4",
+      "26-28"
+    ]
+  },
+  {
+    "id": "event-driven-architecture",
+    "title": "Emits",
+    "description": "We can define the events that this step will emit, this is how we can trigger other Motia Steps.",
+    "lines": [
+      "29",
+      "42-50"
+    ]
+  },
+  {
+    "id": "handler",
+    "title": "Handler",
+    "description": "The handler is the function that will be executed when the step is triggered. This one receives the request body and emits events.",
+    "lines": [
+      "32-52"
+    ]
+  },
+  {
+    "id": "logger",
+    "title": "Logger",
+    "description": "The logger is a utility that allows you to log messages to the console. It is available in the handler function. We encourage you to use it instead of console.log. It will automatically be tied to the trace id of the request.",
+    "lines": [
+      "34"
+    ]
+  },
+  {
+    "id": "http-response",
+    "title": "HTTP Response",
+    "description": "The handler can return a response to the client. This is how we can return a response to the client. It must comply with the responseSchema defined in the step configuration.",
+    "lines": [
+      "52"
+    ]
+  }
+]

package/dist/esm/create/templates/python/tutorial/petstore/process_food_order_step.py-features.json.txt

@@ -0,0 +1,68 @@
+[
+  {
+    "id": "step-configuration",
+    "title": "Step Configuration",
+    "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
+    "lines": [
+      "5-19"
+    ]
+  },
+  {
+    "id": "event-configuration",
+    "title": "Event Step",
+    "description": "Definition of an event step that subscribes to specific topics",
+    "lines": [
+      "12",
+      "15-16"
+    ]
+  },
+  {
+    "id": "input-schema",
+    "title": "Input Schema",
+    "description": "Definition of the expected input data structure from the subscribed topic. Motia will automatically generate types based on this schema.",
+    "lines": [
+      "5-9",
+      "17"
+    ]
+  },
+  {
+    "id": "event-emits",
+    "title": "Emits",
+    "description": "We can define the events that this step will emit, triggering other Motia Steps.",
+    "lines": [
+      "17"
+    ]
+  },
+  {
+    "id": "handler",
+    "title": "Handler",
+    "description": "The handler is the function that will be executed when the step receives an event from its subscribed topic. It processes the input data and can emit new events.",
+    "lines": [
+      "21-50"
+    ]
+  },
+  {
+    "id": "state",
+    "title": "State Management",
+    "description": "The handler demonstrates state management by storing order data that can be accessed by other steps.",
+    "lines": [
+      "35"
+    ]
+  },
+  {
+    "id": "event-emission",
+    "title": "Event Emission",
+    "description": "After processing the order, the handler emits a new event to notify other steps about the new order.",
+    "lines": [
+      "37-50"
+    ]
+  },
+  {
+    "id": "logger",
+    "title": "Logger",
+    "description": "The logger is a utility that allows you to log messages to the console. It is available in the handler function and automatically ties to the trace id of the request.",
+    "lines": [
+      "22"
+    ]
+  }
+]

package/dist/esm/create/templates/python/tutorial/petstore/state_audit_cron_step.py-features.json.txt

@@ -0,0 +1,26 @@
+[
+  {
+    "id": "step-configuration",
+    "title": "Step Configuration",
+    "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
+    "lines": [
+      "3-10"
+    ]
+  },
+  {
+    "id": "cron-configuration",
+    "title": "Cron Configuration",
+    "description": "Cron steps require a specific configuration structure with the 'type' field set to 'cron' and a valid cron expression.",
+    "lines": [
+      "4-5"
+    ]
+  },
+  {
+    "id": "handler",
+    "title": "Cron Step Handler",
+    "description": "The Cron step handler only receives one argument.",
+    "lines": [
+      "12-39"
+    ]
+  }
+]

package/dist/esm/create/templates/python/tutorial/process_food_order_step.py-features.json.txt

@@ -0,0 +1,68 @@
+[
+  {
+    "id": "step-configuration",
+    "title": "Step Configuration",
+    "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
+    "lines": [
+      "5-19"
+    ]
+  },
+  {
+    "id": "event-configuration",
+    "title": "Event Step",
+    "description": "Definition of an event step that subscribes to specific topics",
+    "lines": [
+      "12",
+      "15-16"
+    ]
+  },
+  {
+    "id": "input-schema",
+    "title": "Input Schema",
+    "description": "Definition of the expected input data structure from the subscribed topic. Motia will automatically generate types based on this schema.",
+    "lines": [
+      "5-9",
+      "17"
+    ]
+  },
+  {
+    "id": "event-emits",
+    "title": "Emits",
+    "description": "We can define the events that this step will emit, triggering other Motia Steps.",
+    "lines": [
+      "17"
+    ]
+  },
+  {
+    "id": "handler",
+    "title": "Handler",
+    "description": "The handler is the function that will be executed when the step receives an event from its subscribed topic. It processes the input data and can emit new events.",
+    "lines": [
+      "21-50"
+    ]
+  },
+  {
+    "id": "state",
+    "title": "State Management",
+    "description": "The handler demonstrates state management by storing order data that can be accessed by other steps.",
+    "lines": [
+      "35"
+    ]
+  },
+  {
+    "id": "event-emission",
+    "title": "Event Emission",
+    "description": "After processing the order, the handler emits a new event to notify other steps about the new order.",
+    "lines": [
+      "37-50"
+    ]
+  },
+  {
+    "id": "logger",
+    "title": "Logger",
+    "description": "The logger is a utility that allows you to log messages to the console. It is available in the handler function and automatically ties to the trace id of the request.",
+    "lines": [
+      "22"
+    ]
+  }
+]

package/dist/esm/create/templates/python/tutorial/state_audit_cron_step.py-features.json.txt

@@ -0,0 +1,26 @@
+[
+  {
+    "id": "step-configuration",
+    "title": "Step Configuration",
+    "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
+    "lines": [
+      "3-10"
+    ]
+  },
+  {
+    "id": "cron-configuration",
+    "title": "Cron Configuration",
+    "description": "Cron steps require a specific configuration structure with the 'type' field set to 'cron' and a valid cron expression.",
+    "lines": [
+      "4-5"
+    ]
+  },
+  {
+    "id": "handler",
+    "title": "Cron Step Handler",
+    "description": "The Cron step handler only receives one argument.",
+    "lines": [
+      "12-39"
+    ]
+  }
+]

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "motia",
   "description": "A Modern Unified Backend Framework for APIs, Events and Agents",
-  "version": "0.8.5-beta.142",
+  "version": "0.8.5-beta.143-445618",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -46,9 +46,9 @@
     "python-ast": "^0.1.0",
     "table": "^6.9.0",
     "ts-node": "^10.9.2",
-    "@motiadev/core": "0.8.5-beta.142",
-    "@motiadev/workbench": "0.8.5-beta.142",
-    "@motiadev/stream-client-node": "0.8.5-beta.142"
+    "@motiadev/core": "0.8.5-beta.143-445618",
+    "@motiadev/stream-client-node": "0.8.5-beta.143-445618",
+    "@motiadev/workbench": "0.8.5-beta.143-445618"
   },
   "devDependencies": {
     "@amplitude/analytics-types": "^2.9.2",