motia 0.11.0-beta.154 → 0.11.0-beta.155-562047

package/dist/cjs/create/templates/nodejs/src/services/pet-store.ts.txt

@@ -0,0 +1,29 @@
+import type { Order, Pet } from './types'
+
+export const petStoreService = {
+  createPet: async (pet: Omit<Pet, 'id'>): Promise<Pet> => {
+    const response = await fetch('https://xnigaj-xtnawg.motiahub.com/pet', {
+      method: 'POST',
+      body: JSON.stringify({
+        name: pet?.name ?? '',
+        photoUrls: [pet?.photoUrl ?? ''],
+        status: 'available',
+      }),
+      headers: { 'Content-Type': 'application/json' },
+    })
+    return response.json()
+  },
+  createOrder: async (order: Omit<Order, 'id' | 'complete'>): Promise<Order> => {
+    const response = await fetch('https://xnigaj-xtnawg.motiahub.com/store/order', {
+      method: 'POST',
+      body: JSON.stringify({
+        quantity: order?.quantity ?? 1,
+        petId: order?.petId ?? '1',
+        shipDate: order?.shipDate ?? new Date().toISOString(),
+        status: order?.status ?? 'placed',
+      }),
+      headers: { 'Content-Type': 'application/json' },
+    })
+    return response.json()
+  },
+}

package/dist/{esm/create/templates/nodejs/src/services/pet-store → cjs/create/templates/nodejs/src/services}/types.ts.txt

@@ -1,7 +1,7 @@
 import { z } from 'zod'
 
 export const petSchema = z.object({
-  id: z.number(),
+  id: z.string(),
   name: z.string(),
   photoUrl: z.string(),
 })
@@ -11,9 +11,10 @@ export const orderStatusSchema = z.enum(['placed', 'approved', 'delivered'])
 export const orderSchema = z.object({
   id: z.string(),
   quantity: z.number(),
-  petId: z.number(),
+  petId: z.string(),
   shipDate: z.string(),
   status: orderStatusSchema,
+  complete: z.boolean(),
 })
 
 export type Pet = z.infer<typeof petSchema>

package/dist/cjs/create/templates/nodejs/steps/petstore/api.step.ts.txt

@@ -1,13 +1,13 @@
 import { ApiRouteConfig, Handlers } from 'motia'
 import { z } from 'zod'
-import { petStoreService, petSchema } from '../../src/services/pet-store'
+import { petStoreService } from '../../src/services/pet-store'
+import { petSchema } from '../../src/services/types'
 
 export const config: ApiRouteConfig = {
   type: 'api',
   name: 'ApiTrigger',
   description: 'basic-tutorial api trigger',
   flows: ['basic-tutorial'],
-
   method: 'POST',
   path: '/basic-tutorial',
   bodySchema: z.object({
@@ -17,7 +17,6 @@ export const config: ApiRouteConfig = {
     }),
     foodOrder: z
       .object({
-        id: z.string(),
         quantity: z.number(),
       })
       .optional(),
@@ -29,7 +28,7 @@ export const config: ApiRouteConfig = {
 }
 
 export const handler: Handlers['ApiTrigger'] = async (req, { logger, traceId, emit }) => {
-  logger.info('Step 01 – Processing API Step', { body: req.body })
+  logger.info('Step 01 - Processing API Step', { body: req.body })
 
   const { pet, foodOrder } = req.body
   const newPetRecord = await petStoreService.createPet(pet)
@@ -38,7 +37,7 @@ export const handler: Handlers['ApiTrigger'] = async (req, { logger, traceId, em
     await emit({
       topic: 'process-food-order',
       data: {
-        ...foodOrder,
+        quantity: foodOrder.quantity,
         email: 'test@test.com', // sample email
         petId: newPetRecord.id,
       },

package/dist/cjs/create/templates/nodejs/steps/petstore/process-food-order.step.ts.txt

@@ -10,15 +10,14 @@ export const config: EventConfig = {
   subscribes: ['process-food-order'],
   emits: ['notification'],
   input: z.object({
-    id: z.string(),
     email: z.string(),
     quantity: z.number(),
-    petId: z.number(),
+    petId: z.string(),
   }),
 }
 
 export const handler: Handlers['ProcessFoodOrder'] = async (input, { traceId, logger, state, emit }) => {
-  logger.info('Step 02 – Process food order', { input, traceId })
+  logger.info('Step 02 - Process food order', { input, traceId })
 
   const order = await petStoreService.createOrder({
     ...input,
@@ -26,6 +25,8 @@ export const handler: Handlers['ProcessFoodOrder'] = async (input, { traceId, lo
     status: 'placed',
   })
 
+  logger.info('Order created', { order })
+
   await state.set('orders', order.id, order)
 
   await emit({

package/dist/cjs/create/templates/nodejs/steps/petstore/state-audit-cron.step.ts.txt

@@ -1,4 +1,5 @@
 import { CronConfig, Handlers } from 'motia'
+import { Order } from '../../src/services/types'
 
 export const config: CronConfig = {
   type: 'cron',
@@ -9,15 +10,6 @@ export const config: CronConfig = {
   flows: ['basic-tutorial'],
 }
 
-type Order = {
-  id: number
-  petId: number
-  quantity: number
-  shipDate: string
-  status: string
-  complete: boolean
-}
-
 export const handler: Handlers['StateAuditJob'] = async ({ logger, state, emit }) => {
   const stateValue = await state.getGroup<Order>('orders')
 

package/dist/cjs/create/templates/nodejs/tutorial/petstore/api.step.ts-features.json.txt

@@ -2,66 +2,49 @@
   {
     "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-29"
-    ]
+    "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-28"]
   },
   {
     "id": "api-configuration",
     "title": "API Step",
     "description": "Definition of an API endpoint",
-    "lines": [
-      "11-12"
-    ]
+    "lines": ["7", "11-12"]
   },
   {
     "id": "request-body",
     "title": "Request body",
     "description": "Definition of the expected request body. Motia will automatically generate types based on this schema.",
-    "lines": [
-      "13-24"
-    ]
+    "lines": ["13-23"]
   },
   {
     "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": [
-      "25-27"
-    ]
+    "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": ["24-26"]
   },
   {
     "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": [
-      "28",
-      "38-45"
-    ]
+    "description": "We can define the events that this step will emit. This is how we can trigger other Motia steps.",
+    "lines": ["27", "37-44"]
   },
   {
     "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": [
-      "31-49"
-    ]
+    "lines": ["30-48"]
   },
   {
     "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": [
-      "32"
-    ]
+    "lines": ["31"]
   },
   {
     "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": [
-      "48"
-    ]
+    "description": "The handler can return a response to the client. It must comply with the responseSchema defined in the step configuration.",
+    "lines": ["47"]
   }
-]
+]

package/dist/cjs/create/templates/nodejs/tutorial/petstore/process-food-order.step.ts-features.json.txt

@@ -2,66 +2,49 @@
   {
     "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-17"
-    ]
+    "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-17"]
   },
   {
     "id": "event-configuration",
     "title": "Event Step",
     "description": "Definition of an event step that subscribes to specific topics",
-    "lines": [
-      "6",
-      "10-11"
-    ]
+    "lines": ["6", "10"]
   },
   {
     "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": [
-      "12-16"
-    ]
+    "lines": ["12-16"]
   },
   {
     "id": "event-emits",
     "title": "Emits",
-    "description": "We can define the events that this step will emit, triggering other Motia Steps.",
-    "lines": [
-      "11"
-    ]
+    "description": "We can define the events that this step will emit, triggering other Motia steps.",
+    "lines": ["11"]
   },
   {
     "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": [
-      "19-44"
-    ]
+    "lines": ["19-46"]
   },
   {
     "id": "state",
     "title": "State Management",
     "description": "The handler demonstrates state management by storing order data that can be accessed by other steps.",
-    "lines": [
-      "28"
-    ]
+    "lines": ["30"]
   },
   {
     "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": [
-      "30-43"
-    ]
+    "lines": ["32-45"]
   },
   {
     "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": [
-      "20"
-    ]
+    "lines": ["20", "28"]
   }
-]
+]

package/dist/cjs/create/templates/nodejs/tutorial/petstore/state-audit-cron.step.ts-features.json.txt

@@ -2,25 +2,19 @@
   {
     "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"
-    ]
+    "description": "All steps should have a defined configuration. This is how you define the step's behavior and how it will be triggered.",
+    "lines": ["4-11"]
   },
   {
     "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"
-    ]
+    "lines": ["5-6"]
   },
   {
     "id": "handler",
     "title": "Cron Step Handler",
     "description": "The Cron step handler only receives one argument.",
-    "lines": [
-      "21-51"
-    ]
+    "lines": ["13-43"]
   }
-]
+]

package/dist/cjs/create/templates/nodejs/tutorial/tutorial.tsx.txt

@@ -29,7 +29,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.flows.node('apitrigger'),
     title: 'API Step',
-    link: 'https://www.motia.dev/docs/concepts/steps#api-trigger',
+    link: 'https://www.motia.dev/docs/concepts/steps#triggers-api',
     description: () => (
       <p>
         Let's evaluate the Step that will allow you to receive traffic from external applications, API Steps will allow
@@ -156,7 +156,6 @@ export const steps: TutorialStep[] = [
         object as the first argument, followed by a second argument that provides access to the <b>logger</b>,{' '}
         <b>event emitter</b>, <b>state manager</b>, and <b>trace id</b>.<br />
         <br />
-        <br />
         💡 We will cover these in depth further down the tutorial.
       </p>
     ),
@@ -188,10 +187,8 @@ export const steps: TutorialStep[] = [
       <p>
         Now let's wrap our API Step and return a response.
         <br />
-        <br />
-        <br />
-        You simply need to return an object that complies with one of the <b>responseSchema</b> definitions
-        declared in your Step configuration.
+        You simply need to return an object that complies with one of the <b>responseSchema</b> definitions declared in
+        your Step configuration.
       </p>
     ),
     before: [{ type: 'click', selector: workbenchXPath.flows.feature('http-response') }],
@@ -202,7 +199,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.flows.node('processfoodorder'),
     title: 'Event Step',
-    link: 'https://www.motia.dev/docs/concepts/steps#event-trigger',
+    link: 'https://www.motia.dev/docs/concepts/steps#triggers-event',
     description: () => (
       <p>
         Now that we have an entry point in our flow, let's focus on subscribing to a <b>topic</b> and performing a
@@ -212,8 +209,8 @@ export const steps: TutorialStep[] = [
         For this we will look at the <b>Event</b> Step.
         <br />
         <br />
-        <b> Event</b> Steps are essential for Motia's event driven architecture. Let's dive deeper into the
-        anatomy of an Event Step by taking a look at the code visualization tool.
+        <b> Event</b> Steps are essential for Motia's event driven architecture. Let's dive deeper into the anatomy of
+        an Event Step by taking a look at the code visualization tool.
         <br />
         <br />
         💡 <b>Event</b> Steps can only be triggered internally, through topic subscriptions.
@@ -224,7 +221,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.sidebarContainer,
     title: 'Event Step',
-    link: 'https://www.motia.dev/docs/concepts/steps#event-trigger',
+    link: 'https://www.motia.dev/docs/concepts/steps#triggers-event',
     description: () => (
       <p>
         Now that we have an entry point in our flow, let's focus on subscribing to a <b>topic</b> and performing a
@@ -232,8 +229,8 @@ export const steps: TutorialStep[] = [
         <br /> <br />
         For this we will look at the <b>Event</b> Step.
         <br /> <br />
-        <b> Event</b> Steps are essential for Motia's event driven architecture. Let's dive deeper into the
-        anatomy of an Event Step by taking a look at the code visualization tool.
+        <b> Event</b> Steps are essential for Motia's event driven architecture. Let's dive deeper into the anatomy of
+        an Event Step by taking a look at the code visualization tool.
         <br /> <br />
         💡 <b>Event</b> Steps can only be triggered internally, through topic subscriptions.
       </p>
@@ -301,7 +298,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.flows.node('stateauditjob'),
     title: 'Cron Step',
-    link: 'https://www.motia.dev/docs/concepts/steps#cron-trigger',
+    link: 'https://www.motia.dev/docs/concepts/steps#triggers-cron',
     description: () => (
       <p>
         Let's do a recap of what you've learned, thus far you've become familiar with two Step types <b>API</b>{' '}
@@ -317,7 +314,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.sidebarContainer,
     title: 'Cron Schedule',
-    link: 'https://www.motia.dev/docs/concepts/steps#cron-trigger',
+    link: 'https://www.motia.dev/docs/concepts/steps#triggers-cron',
     description: () => (
       <p>
         <b>CRON</b> Steps are similar to the other Step types, they are composed by a configuration and a handler.
@@ -353,7 +350,7 @@ export const steps: TutorialStep[] = [
     before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
   },
 
-  // // Endpoints
+  // Endpoints
 
   {
     elementXpath: workbenchXPath.links.endpoints,
@@ -397,7 +394,7 @@ export const steps: TutorialStep[] = [
     description: () => (
       <p>
         Once you click on an endpoint from the list, you will be able to test it by providing a request payload and
-        clicking on the <b>Play</b> button.
+        clicking on the <b>Send</b> button.
         <br />
         <br />
         This section will provide an overview of your API endpoint.
@@ -437,16 +434,13 @@ export const steps: TutorialStep[] = [
           This form will allow you to validate your API Step by executing an HTTP request against your API endpoint.
         </p>
         <br />
-        <br />
         <p>You can also test your API endpoints using your terminal through the curl command.</p>
         <br />
-        <br />
         <p>
           💡 Thanks to the <b>bodySchema</b> attribute from the API Step config, you are automatically provided with a
           sample request payload.
         </p>
         <br />
-        <br />
         <pre className="code-preview">
           <code className="language-bash">
             curl -X POST http://localhost:3000/basic-tutorial \<br />
@@ -454,7 +448,7 @@ export const steps: TutorialStep[] = [
             {'  '}-d '
             {JSON.stringify({
               pet: { name: 'Jack', photoUrl: 'https://images.dog.ceo/breeds/pug/n02110958_13560.jpg' },
-              foodOrder: { id: 'food-order-1', quantity: 0 },
+              foodOrder: { quantity: 1 },
             })}
             '
           </code>
@@ -471,7 +465,7 @@ export const steps: TutorialStep[] = [
     title: 'API Endpoint Test',
     description: () => (
       <p>
-        Once you've filled the request payload, you can click on the <b>Play</b> button to trigger an HTTP request
+        Once you've filled the request payload, you can click on the <b>Send</b> button to trigger an HTTP request
         against your API endpoint.
       </p>
     ),
@@ -480,7 +474,7 @@ export const steps: TutorialStep[] = [
         type: 'fill-editor',
         content: {
           pet: { name: 'Jack', photoUrl: 'https://images.dog.ceo/breeds/pug/n02110958_13560.jpg' },
-          foodOrder: { id: 'food-order-1', quantity: 0 },
+          foodOrder: { quantity: 1 },
         },
       },
     ],

package/dist/cjs/create/templates/python/src/services/pet_store.py.txt

@@ -12,7 +12,7 @@ class PetStoreService:
         
         async with httpx.AsyncClient() as client:
             response = await client.post(
-                'https://petstore.swagger.io/v2/pet',
+                'https://xnigaj-xtnawg.motiahub.com/pet',
                 json=pet_data,
                 headers={'Content-Type': 'application/json'}
             )
@@ -22,13 +22,13 @@ class PetStoreService:
         async with httpx.AsyncClient() as client:
             order_data = {
                 "quantity": order.get("quantity", 1),
-                "petId": 1,
+                "petId": order.get("pet_id", '1'),
                 "shipDate": order.get("ship_date", "2025-08-22T22:07:04.730Z"),
                 "status": order.get("status", "placed"),
             }
             
             response = await client.post(
-                'https://petstore.swagger.io/v2/store/order',
+                'https://xnigaj-xtnawg.motiahub.com/store/order',
                 json=order_data,
                 headers={'Content-Type': 'application/json'}
             )

package/dist/cjs/create/templates/python/src/services/types.py.txt

@@ -7,13 +7,14 @@ class OrderStatus(str, Enum):
     DELIVERED = "delivered"
 
 class Pet(BaseModel):
-    id: int
+    id: str
     name: str
     photoUrl: str
 
 class Order(BaseModel):
     id: str
     quantity: int
-    petId: int
+    petId: str
     shipDate: str
     status: OrderStatus
+    complete: bool

package/dist/cjs/create/templates/python/steps/petstore/api_step.py.txt

@@ -8,7 +8,6 @@ class PetRequest(BaseModel):
     photoUrl: str
 
 class FoodOrder(BaseModel):
-    id: str
     quantity: int
 
 class RequestBody(BaseModel):
@@ -31,7 +30,7 @@ config = {
 
 async def handler(req, context):
     body = req.get("body", {})
-    context.logger.info("Step 01 – Processing API Step", {"body": body})
+    context.logger.info("Step 01 - Processing API Step", {"body": body})
 
     pet = body.get("pet", {})
     food_order = body.get("foodOrder", {})
@@ -42,11 +41,10 @@ async def handler(req, context):
         await context.emit({
             "topic": "process-food-order",
             "data": {
-                "id": food_order.get("id"),
                 "quantity": food_order.get("quantity"),
                 "email": "test@test.com",  # sample email
                 "pet_id": new_pet_record.get("id"),
             },
         })
 
-    return {"status": 200, "body": {**new_pet_record, "traceId": context.trace_id}}
+    return {"status": 200, "body": {**new_pet_record, "traceId": context.trace_id}}

package/dist/cjs/create/templates/python/steps/petstore/process_food_order_step.py.txt

@@ -3,10 +3,9 @@ from datetime import datetime
 from src.services.pet_store import pet_store_service
 
 class InputSchema(BaseModel):
-    id: str
     email: str
     quantity: int
-    pet_id: int
+    pet_id: str
 
 config = {
     "type": "event",
@@ -19,10 +18,9 @@ config = {
 }
 
 async def handler(input_data, context):
-    context.logger.info("Step 02 – Process food order", {"input": input_data})
+    context.logger.info("Step 02 - Process food order", {"input": input_data, "traceId": context.trace_id})
 
     order = await pet_store_service.create_order({
-        "id": input_data.get("id"),
         "quantity": input_data.get("quantity"),
         "pet_id": input_data.get("pet_id"),
         "email": input_data.get("email"),

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

@@ -3,67 +3,48 @@
     "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"
-    ]
+    "lines": ["6-29"]
   },
   {
     "id": "api-configuration",
     "title": "API Step",
     "description": "Definition of an API endpoint",
-    "lines": [
-      "23-24"
-    ]
+    "lines": ["18", "22-23"]
   },
   {
     "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"
-    ]
+    "lines": ["6-15", "24"]
   },
   {
     "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"
-    ]
+    "lines": ["4", "25-27"]
   },
   {
     "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"
-    ]
+    "lines": ["28", "41-48"]
   },
   {
     "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"
-    ]
+    "lines": ["31-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. We encourage you to use it instead of console.log. It will automatically be tied to the trace id of the request.",
-    "lines": [
-      "34"
-    ]
+    "lines": ["33"]
   },
   {
     "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"
-    ]
+    "lines": ["50"]
   }
-]
+]