motia 0.14.0-beta.165-285707 → 0.15.0-beta.165

package/dist/esm/create/templates/index.ts

@@ -1,10 +0,0 @@
-import { type Generator, generatePluginTemplate, generateTemplateSteps } from './generate'
-
-export const templates: Record<string, Generator> = {
-  'motia-tutorial-typescript': generateTemplateSteps('nodejs'),
-  'motia-tutorial-python': generateTemplateSteps('python'),
-  plugin: generatePluginTemplate('plugin'),
-  'starter-typescript': generateTemplateSteps('hello'),
-  'starter-javascript': generateTemplateSteps('hello_js'),
-  'starter-python': generateTemplateSteps('hello_python'),
-}

package/dist/esm/create/templates/nodejs/README.md.txt

@@ -1,93 +0,0 @@
-# {{PROJECT_NAME}}
-
-A Motia tutorial project in TypeScript.
-
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
-
-## Quick Start
-
-```bash
-# Start the development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-```
-
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-1. **Open the Workbench** in your browser at [`http://localhost:3000`](http://localhost:3000)
-2. **Click the `Tutorial`** button on the top right of the workbench
-3. **Complete the `Tutorial`** to get an understanding of the basics of Motia and using the Workbench
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
-
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
-
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
-
-## Project Structure
-
-```
-steps/              # Your Step definitions (or use src/)
-src/                # Shared services and utilities
-motia.config.ts     # Motia configuration
-```
-
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
-
-## Tutorial
-
-This project includes an interactive tutorial that will guide you through:
-- Understanding Steps and their types
-- Creating API endpoints
-- Building event-driven workflows
-- Using state management
-- Observing your flows in the Workbench
-
-## Learn More
-
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
-- [Discord Community](https://discord.gg/motia) - Get help and connect with other developers
-

package/dist/esm/create/templates/nodejs/motia-workbench.json

@@ -1,27 +0,0 @@
-[
-  {
-    "id": "basic-tutorial",
-    "config": {
-      "steps/petstore/state-audit-cron.step.ts": {
-        "x": -175,
-        "y": 219,
-        "sourceHandlePosition": "right"
-      },
-      "steps/petstore/process-food-order.step.ts": {
-        "x": 144,
-        "y": 17,
-        "sourceHandlePosition": "bottom"
-      },
-      "steps/petstore/notification.step.ts": {
-        "x": 331,
-        "y": 261,
-        "sourceHandlePosition": "bottom"
-      },
-      "steps/petstore/api.step.ts": {
-        "x": -175,
-        "y": 3,
-        "sourceHandlePosition": "right"
-      }
-    }
-  }
-]

package/dist/esm/create/templates/nodejs/motia.config.ts.txt

@@ -1,10 +0,0 @@
-import { config } from '@motiadev/core'
-const statesPlugin = require('@motiadev/plugin-states/plugin')
-const endpointPlugin = require('@motiadev/plugin-endpoint/plugin')
-const logsPlugin = require('@motiadev/plugin-logs/plugin')
-const observabilityPlugin = require('@motiadev/plugin-observability/plugin')
-const bullmqPlugin = require('@motiadev/plugin-bullmq/plugin')
-
-export default config({
-  plugins: [observabilityPlugin, statesPlugin, endpointPlugin, logsPlugin, bullmqPlugin],
-})

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

@@ -1,29 +0,0 @@
-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/types.ts.txt

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

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

@@ -1,48 +0,0 @@
-import { ApiRouteConfig, Handlers } from 'motia'
-import { z } from 'zod'
-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({
-    pet: z.object({
-      name: z.string(),
-      photoUrl: z.string(),
-    }),
-    foodOrder: z
-      .object({
-        quantity: z.number(),
-      })
-      .optional(),
-  }),
-  responseSchema: {
-    200: petSchema,
-  },
-  emits: ['process-food-order'],
-}
-
-export const handler: Handlers['ApiTrigger'] = async (req, { logger, traceId, emit }) => {
-  logger.info('Step 01 - Processing API Step', { body: req.body })
-
-  const { pet, foodOrder } = req.body
-  const newPetRecord = await petStoreService.createPet(pet)
-
-  if (foodOrder) {
-    await emit({
-      topic: 'process-food-order',
-      data: {
-        quantity: foodOrder.quantity,
-        email: 'test@test.com', // sample email
-        petId: newPetRecord.id,
-      },
-    })
-  }
-
-  return { status: 200, body: { ...newPetRecord, traceId } }
-}

package/dist/esm/create/templates/nodejs/steps/petstore/notification.step.ts.txt

@@ -1,35 +0,0 @@
-import { EventConfig, Handlers } from 'motia'
-import { z } from 'zod'
-
-export const config: EventConfig = {
-  type: 'event',
-  name: 'Notification',
-  description: 'Sends notifications to users',
-  flows: ['basic-tutorial'],
-  subscribes: ['notification'],
-  emits: [],
-  input: z.object({
-    templateId: z.string(),
-    email: z.string(),
-    templateData: z.record(z.string(), z.any()),
-  }),
-}
-
-export const handler: Handlers['Notification'] = async (input, { traceId, logger }) => {
-  const { email, ...data } = input
-  const redactedEmail = email.replace(/(?<=.{2}).(?=.*@)/g, '*')
-
-  logger.info('Processing Notification', { data, email: redactedEmail })
-
-  /*
-   * This represents a call to some sort of
-   * notification service to indicate that a
-   * new order has been placed
-   */
-  logger.info('New notification sent', {
-    templateId: data.templateId,
-    email: redactedEmail,
-    templateData: data.templateData,
-    traceId,
-  })
-}

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

@@ -1,46 +0,0 @@
-import { EventConfig, Handlers } from 'motia'
-import { z } from 'zod'
-import { petStoreService } from '../../src/services/pet-store'
-
-export const config: EventConfig = {
-  type: 'event',
-  name: 'ProcessFoodOrder',
-  description: 'basic-tutorial event step, demonstrates how to consume an event from a topic and persist data in state',
-  flows: ['basic-tutorial'],
-  subscribes: ['process-food-order'],
-  emits: ['notification'],
-  input: z.object({
-    email: z.string(),
-    quantity: 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 })
-
-  const order = await petStoreService.createOrder({
-    ...input,
-    shipDate: new Date().toISOString(),
-    status: 'placed',
-  })
-
-  logger.info('Order created', { order })
-
-  await state.set('orders', order.id, order)
-
-  await emit({
-    topic: 'notification',
-    data: {
-      email: input.email,
-      templateId: 'new-order',
-      templateData: {
-        status: order.status,
-        shipDate: order.shipDate,
-        id: order.id,
-        petId: order.petId,
-        quantity: order.quantity,
-      },
-    },
-  })
-}

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

@@ -1,43 +0,0 @@
-import { CronConfig, Handlers } from 'motia'
-import { Order } from '../../src/services/types'
-
-export const config: CronConfig = {
-  type: 'cron',
-  cron: '0 0 * * 1', // run once every Monday at midnight
-  name: 'StateAuditJob',
-  description: 'Checks the state for orders that are not complete and have a ship date in the past',
-  emits: ['notification'],
-  flows: ['basic-tutorial'],
-}
-
-export const handler: Handlers['StateAuditJob'] = async ({ logger, state, emit }) => {
-  const stateValue = await state.getGroup<Order>('orders')
-
-  for (const item of stateValue) {
-    // check if current date is after item.shipDate
-    const currentDate = new Date()
-    const shipDate = new Date(item.shipDate)
-
-    if (!item.complete && currentDate > shipDate) {
-      logger.warn('Order is not complete and ship date is past', {
-        orderId: item.id,
-        shipDate: item.shipDate,
-        complete: item.complete,
-      })
-
-      await emit({
-        topic: 'notification',
-        data: {
-          email: 'test@test.com',
-          templateId: 'order-audit-warning',
-          templateData: {
-            orderId: item.id,
-            status: item.status,
-            shipDate: item.shipDate,
-            message: 'Order is not complete and ship date is past',
-          },
-        },
-      })
-    }
-  }
-}

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

@@ -1,50 +0,0 @@
-[
-  {
-    "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-28"]
-  },
-  {
-    "id": "api-configuration",
-    "title": "API Step",
-    "description": "Definition of an API endpoint",
-    "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-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": ["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": ["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": ["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": ["31"]
-  },
-  {
-    "id": "http-response",
-    "title": "HTTP Response",
-    "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/esm/create/templates/nodejs/tutorial/petstore/process-food-order.step.ts-features.json.txt

@@ -1,50 +0,0 @@
-[
-  {
-    "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"]
-  },
-  {
-    "id": "event-configuration",
-    "title": "Event Step",
-    "description": "Definition of an event step that subscribes to specific topics",
-    "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"]
-  },
-  {
-    "id": "event-emits",
-    "title": "Emits",
-    "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-46"]
-  },
-  {
-    "id": "state",
-    "title": "State Management",
-    "description": "The handler demonstrates state management by storing order data that can be accessed by other steps.",
-    "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": ["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", "28"]
-  }
-]

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

@@ -1,20 +0,0 @@
-[
-  {
-    "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": ["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": ["5-6"]
-  },
-  {
-    "id": "handler",
-    "title": "Cron Step Handler",
-    "description": "The Cron step handler only receives one argument.",
-    "lines": ["13-43"]
-  }
-]