motia 0.5.11-beta.120-742949 → 0.5.11-beta.120-110250

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

@@ -14,11 +14,6 @@ export const generateTemplateSteps = (templateFolder: string): Generator => {
       for (const fileName of files) {
         const filePath = path.join(templatePath, fileName)
 
-        if (statSync(filePath).isDirectory() && !filePath.match(/services|utils|lib/)) {
-          // ignore folders
-          continue
-        }
-
         if (statSync(filePath).isDirectory()) {
           const folderPath = path.basename(filePath)
           mkdirSync(path.join(rootDir, templateFolder, folderPath))

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "motia",
   "description": "A Modern Unified Backend Framework for APIs, Events and Agents",
-  "version": "0.5.11-beta.120-742949",
+  "version": "0.5.11-beta.120-110250",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -43,9 +43,9 @@
     "inquirer": "^8.2.5",
     "table": "^6.9.0",
     "ts-node": "^10.9.2",
-    "@motiadev/stream-client-node": "0.5.11-beta.120-742949",
-    "@motiadev/workbench": "0.5.11-beta.120-742949",
-    "@motiadev/core": "0.5.11-beta.120-742949"
+    "@motiadev/core": "0.5.11-beta.120-110250",
+    "@motiadev/stream-client-node": "0.5.11-beta.120-110250",
+    "@motiadev/workbench": "0.5.11-beta.120-110250"
   },
   "devDependencies": {
     "@amplitude/analytics-types": "^2.9.2",

package/dist/cjs/create/setup-tutorial-flow.d.ts

@@ -1,6 +0,0 @@
-import { CliContext } from '@/cloud/config-utils';
-type Args = {
-    context: CliContext;
-};
-export declare const createTutorialFlow: ({ context }: Args) => Promise<void>;
-export {};

package/dist/cjs/create/setup-tutorial-flow.js

@@ -1,30 +0,0 @@
-"use strict";
-var __importDefault = (this && this.__importDefault) || function (mod) {
-    return (mod && mod.__esModule) ? mod : { "default": mod };
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.createTutorialFlow = void 0;
-const path_1 = __importDefault(require("path"));
-const fs_1 = __importDefault(require("fs"));
-const utils_1 = require("./utils");
-const setup_template_1 = require("./setup-template");
-const createTutorialFlow = async ({ context }) => {
-    const rootDir = process.cwd();
-    if (!(0, utils_1.checkIfFileExists)(rootDir, 'motia-workbench.json')) {
-        context.log('invalid-project', (message) => message
-            .tag('failed')
-            .append('In order to setup the Motia tutorial you need to be in a valid Motia project, motia-workbench.json not found, if this is not a Motia project you can create one using the motia create cli command.'));
-        return;
-    }
-    const stepsDir = path_1.default.join(rootDir, 'steps');
-    if (!(0, utils_1.checkIfDirectoryExists)(stepsDir)) {
-        fs_1.default.mkdirSync(stepsDir);
-        context.log('steps-directory-created', (message) => message.tag('success').append('Folder').append('steps', 'cyan').append('has been created.'));
-    }
-    if (!(0, utils_1.checkIfDirectoryExists)(path_1.default.join(stepsDir, 'basic-tutorial'))) {
-        fs_1.default.mkdirSync(path_1.default.join(stepsDir, 'basic-tutorial'));
-    }
-    await (0, setup_template_1.setupTemplate)('basic-tutorial', stepsDir, context);
-    context.log('tutorial-flow-setup-completed', (message) => message.tag('success').append('Tutorial flow setup completed, you can now start the tutorial from Workbench.'));
-};
-exports.createTutorialFlow = createTutorialFlow;

package/dist/cjs/create/templates/basic-tutorial/03-state-audit-cron.step.ts.txt

@@ -1,42 +0,0 @@
-import { CronConfig, Handlers } from 'motia'
-
-export const config: CronConfig = {
-  type: 'cron' as const,
-  name: 'StateAuditJob',
-  description: 'Runs every minute and emits a timestamp',
-  cron: '*/5 * * * *', // run every hour at minute 0
-  emits: ['order-audit-error', 'order-audit-warning'],
-  flows: ['basic-tutorial'],
-}
-
-export const handler: Handlers['StateAuditJob'] = async ({ state, emit }) => {
-  const stateValue = await state.getGroup<{
-    id: number
-    petId: number
-    quantity: number
-    shipDate: string
-    status: string
-    complete: boolean
-  }>('orders')
-
-  if (!Array.isArray(stateValue)) {
-    await emit({
-      topic: 'state-audit-error',
-      data: { message: 'State value is not an array' },
-    })
-
-    return
-  }
-
-  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) {
-      await emit({
-        topic: 'order-audit-warning',
-        data: { message: 'Order is not complete and ship date is past' },
-      })
-    }
-  }
-}

package/dist/cjs/create/templates/basic-tutorial/04_new_order_notifications.step.py.txt

@@ -1,27 +0,0 @@
-from pydantic import BaseModel, Field
-
-class NewOrderNotificationInput(BaseModel):
-    order_id: str = Field(description="pet store order id")
-
-config = {
-    "type": "event",
-    "name": "NewOrderNotifications",
-    "description": "Checks a state change using python",
-    "subscribes": ["new-order-notification"],
-    "emits": [],
-    "flows": ["basic-tutorial"],
-    "input": NewOrderNotificationInput.model_json_schema(),
-}
-
-async def handler(input, ctx):
-    ctx.logger.info('Processing NewOrderNotifications', input)
-    ctx.logger.info('[NewOrderNotifications] order id', input.get('order_id'))
-
-    order = await ctx.state.get('orders', input.get('order_id'))
-    
-    # This represents a call to some sort of notification service ot indicate that a new order has been placed
-    ctx.logger.info('New order notification sent using Python: ', {
-        'order_id': input.get('order_id'),
-        'order': order,
-        'trace_id': ctx.trace_id
-    })

package/dist/cjs/create/templates/basic-tutorial/motia-workbench.json

@@ -1,28 +0,0 @@
-[
-  {
-    "id": "basic-tutorial",
-    "config": {
-      "steps/basic-tutorial/04_new_order_notifications.step.py": {
-        "x": 668,
-        "y": 266,
-        "targetHandlePosition": "left"
-      },
-      "steps/basic-tutorial/03-state-audit-cron.step.ts": {
-        "x": 224,
-        "y": 520
-      },
-      "steps/basic-tutorial/02-process-food-order.step.ts": {
-        "x": 220,
-        "y": 242,
-        "sourceHandlePosition": "right",
-        "targetHandlePosition": "left"
-      },
-      "steps/basic-tutorial/01-api.step.ts": {
-        "x": -243,
-        "y": 199,
-        "sourceHandlePosition": "right",
-        "targetHandlePosition": "left"
-      }
-    }
-  }
-]

package/dist/cjs/create/templates/basic-tutorial/services/pet-store.ts.txt

@@ -1,32 +0,0 @@
-export const petStoreService = {
-  createPet: async (pet: { name: string; photoUrl: string }) => {
-    const response = await fetch('https://petstore.swagger.io/v2/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: { id: string; quantity: number; petId: number }) => {
-    const response = await fetch('https://petstore.swagger.io/v2/store/order', {
-      method: 'POST',
-      body: JSON.stringify({
-        id: order.id,
-        quantity: order.quantity,
-        petId: order.petId,
-        shipDate: new Date().toISOString(),
-        status: 'placed',
-      }),
-      headers: {
-        'Content-Type': 'application/json',
-      },
-    })
-    return response.json()
-  },
-}

package/dist/cjs/create/templates/default/00-noop.step.ts.txt

@@ -1,33 +0,0 @@
-import { NoopConfig } from 'motia'
-
-/**
- * NOOP Steps don"t hold any logic in code. They are a way
- * to create custom nodes for flows on the workbench and
- * represent external actions such as human in the loop.
- * 
- * In this case, we are using it to add a custom UI 
- * node with a play button to allow you to trigger the first 
- * API step in this flow.
- *
- * For more information, refer to the documentation: https://www.motia.dev/docs/workbench/noop-steps
- */
-export const config: NoopConfig = {
-  type: 'noop',
-  name: 'Flow Starter',
-  description: 'Start the default flow',
-
-  /**
-   * Used mostly to connect nodes that emit to this
-   */
-  virtualSubscribes: [],
-
-  /**
-   * Used mostly to connect nodes that subscribes to this
-   */
-  virtualEmits: ['/default'],
-
-  /**
-   * The flows this step belongs to, will be available in Workbench
-   */
-  flows: ['default'],
-}

package/dist/cjs/create/templates/default/00-noop.step.tsx.txt

@@ -1,18 +0,0 @@
-import React from 'react'
-import { BaseNode, NoopNodeProps } from 'motia/workbench'
-import { Button } from '@motiadev/ui'
-
-/**
- * For more information on how to override UI nodes, check documentation https://www.motia.dev/docs/workbench/ui-steps
- */
-export const Node: React.FC<NoopNodeProps> = (data) => {
-  const start = () => {
-    fetch('/default', { method: 'POST', body: JSON.stringify({ message: 'test' }) })
-  }
-
-  return (
-    <BaseNode title="Start" variant="noop" {...data} disableTargetHandle>
-      <Button variant="accent" data-testid="start-flow-button" onClick={start}>Start Flow</Button>
-    </BaseNode>
-  )
-}

package/dist/cjs/create/templates/default/01-api.step.ts.txt

@@ -1,70 +0,0 @@
-import { ApiRouteConfig, Handlers } from 'motia'
-import { z } from 'zod'
-
-export const config: ApiRouteConfig = {
-  type: 'api',
-  name: 'ApiTrigger',
-  description: 'default template api trigger',
-
-  method: 'POST',
-  path: '/default',
-
-  /**
-   * This API Step emits events to topic `test-state`
-   */
-  emits: ['test-state'],
-
-  /** 
-   * Expected request body for type checking and documentation
-   */
-  bodySchema: z.object({ message: z.string() }),
-
-  /** 
-   * Expected response body for type checking and documentation
-   */
-  responseSchema: {
-    200: z.object({ 
-      message: z.string(),
-      traceId: z.string(),
-    })
-  },
-
-  /** 
-   * We're using virtual subscribes to virtually connect noop step
-   * to this step.
-   *
-   * Noop step is defined in noop.step.ts
-   */
-  virtualSubscribes: ['/default'],
-
-  /**
-   * The flows this step belongs to, will be available in Workbench
-   */
-  flows: ['default'],
-}
-
-export const handler: Handlers['ApiTrigger'] = async (req, { logger, emit, traceId }) => {
-  /** 
-   * Avoid usage of console.log, use logger instead
-   */
-  logger.info('Step 01 – Processing API Step', { body: req.body })
-
-  /**
-   * Emit events to the topics to process asynchronously
-   */
-  await emit({
-    topic: 'test-state',
-    data: { message: req.body.message },
-  })
-
-  /**
-   * Return data back to the client
-   */
-  return {
-    status: 200,
-    body: {
-      traceId,
-      message: 'test-state topic emitted',
-    },
-  }
-}

package/dist/cjs/create/templates/default/02-test-state.step.ts.txt

@@ -1,53 +0,0 @@
-import { EventConfig, Handlers } from 'motia'
-import { z } from 'zod'
-
-export const config: EventConfig = {
-  type: 'event',
-  name: 'SetStateChange',
-  description: 'set a state change for evaluation',
-
-  /**
-   * This step subscribes to the event `test-state` to 
-   * be processed asynchronously.
-   */
-  subscribes: ['test-state'],
-
-  /**
-   * It ultimately emits an event to `check-state-change` topic.
-   */
-  emits: ['check-state-change'],
-
-  /**
-   * Definition of the expected input
-   */
-  input: z.object({ message: z.string() }),
-
-  /**
-   * The flows this step belongs to, will be available in Workbench
-   */
-  flows: ['default'],
-}
-
-export const handler: Handlers['SetStateChange'] = async (input, { traceId, logger, state, emit }) => {
-  /** 
-   * Avoid usage of console.log, use logger instead
-   */
-  logger.info('Step 02 – Pushing message content to state', { input })
-
-  const message = 'Welcome to motia!'
-
-  /**
-   * Persist content on state to be used by other steps
-   * or in other workflows later
-   */
-  await state.set<string>(traceId, 'test', message)
-
-  /**
-   * Emit events to the topics to process separately
-   * on another step
-   */
-  await emit({
-    topic: 'check-state-change',
-    data: { key: 'test', expected: message }
-  })
-}

package/dist/cjs/create/templates/default/03-check-state-change.step.ts.txt

@@ -1,54 +0,0 @@
-import { EventConfig, Handlers } from 'motia'
-import { z } from 'zod'
-
-export const config: EventConfig = {
-  type: 'event',
-  name: 'CheckStateChange',
-  description: 'check state change',
-
-  /**
-   * This step subscribes to the event `check-state-change` to 
-   * be processed asynchronously.
-   */
-  subscribes: ['check-state-change'],
-
-  /**
-   * Doesn't emit anything, which means this is a final step in a workflow
-   */
-  emits: [],
-
-  /**
-   * Definition of the expected input
-   */
-  input: z.object({ key: z.string(), expected: z.string() }),
-  
-  /**
-   * The flows this step belongs to, will be available in Workbench
-   */
-  flows: ['default'],
-}
-
-export const handler: Handlers['CheckStateChange'] = async (input, { traceId, logger, state }) => {
-  /** 
-   * Avoid usage of console.log, use logger instead
-   */
-  logger.info('Step 03 – Executing CheckStateChange step', { input })
-
-  /**
-   * Fetches value from state with the given key
-   */
-  const value = await state.get<string>(traceId, input.key)
-
-  if (value !== input.expected) {
-    logger.error('The provided value for the state key does not match', { 
-      key: input.key,
-      value,
-      expected: input.expected
-    })
-  } else {
-    logger.info('The provided value matches the state value 🏁', {
-      key: input.key,
-      value,
-    })
-  }
-}

package/dist/esm/create/setup-tutorial-flow.d.ts

@@ -1,6 +0,0 @@
-import { CliContext } from '@/cloud/config-utils';
-type Args = {
-    context: CliContext;
-};
-export declare const createTutorialFlow: ({ context }: Args) => Promise<void>;
-export {};

package/dist/esm/create/setup-tutorial-flow.js

@@ -1,23 +0,0 @@
-import path from 'path';
-import fs from 'fs';
-import { checkIfDirectoryExists, checkIfFileExists } from './utils';
-import { setupTemplate } from './setup-template';
-export const createTutorialFlow = async ({ context }) => {
-    const rootDir = process.cwd();
-    if (!checkIfFileExists(rootDir, 'motia-workbench.json')) {
-        context.log('invalid-project', (message) => message
-            .tag('failed')
-            .append('In order to setup the Motia tutorial you need to be in a valid Motia project, motia-workbench.json not found, if this is not a Motia project you can create one using the motia create cli command.'));
-        return;
-    }
-    const stepsDir = path.join(rootDir, 'steps');
-    if (!checkIfDirectoryExists(stepsDir)) {
-        fs.mkdirSync(stepsDir);
-        context.log('steps-directory-created', (message) => message.tag('success').append('Folder').append('steps', 'cyan').append('has been created.'));
-    }
-    if (!checkIfDirectoryExists(path.join(stepsDir, 'basic-tutorial'))) {
-        fs.mkdirSync(path.join(stepsDir, 'basic-tutorial'));
-    }
-    await setupTemplate('basic-tutorial', stepsDir, context);
-    context.log('tutorial-flow-setup-completed', (message) => message.tag('success').append('Tutorial flow setup completed, you can now start the tutorial from Workbench.'));
-};

package/dist/esm/create/templates/basic-tutorial/03-state-audit-cron.step.ts.txt

@@ -1,42 +0,0 @@
-import { CronConfig, Handlers } from 'motia'
-
-export const config: CronConfig = {
-  type: 'cron' as const,
-  name: 'StateAuditJob',
-  description: 'Runs every minute and emits a timestamp',
-  cron: '*/5 * * * *', // run every hour at minute 0
-  emits: ['order-audit-error', 'order-audit-warning'],
-  flows: ['basic-tutorial'],
-}
-
-export const handler: Handlers['StateAuditJob'] = async ({ state, emit }) => {
-  const stateValue = await state.getGroup<{
-    id: number
-    petId: number
-    quantity: number
-    shipDate: string
-    status: string
-    complete: boolean
-  }>('orders')
-
-  if (!Array.isArray(stateValue)) {
-    await emit({
-      topic: 'state-audit-error',
-      data: { message: 'State value is not an array' },
-    })
-
-    return
-  }
-
-  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) {
-      await emit({
-        topic: 'order-audit-warning',
-        data: { message: 'Order is not complete and ship date is past' },
-      })
-    }
-  }
-}

package/dist/esm/create/templates/basic-tutorial/04_new_order_notifications.step.py.txt

@@ -1,27 +0,0 @@
-from pydantic import BaseModel, Field
-
-class NewOrderNotificationInput(BaseModel):
-    order_id: str = Field(description="pet store order id")
-
-config = {
-    "type": "event",
-    "name": "NewOrderNotifications",
-    "description": "Checks a state change using python",
-    "subscribes": ["new-order-notification"],
-    "emits": [],
-    "flows": ["basic-tutorial"],
-    "input": NewOrderNotificationInput.model_json_schema(),
-}
-
-async def handler(input, ctx):
-    ctx.logger.info('Processing NewOrderNotifications', input)
-    ctx.logger.info('[NewOrderNotifications] order id', input.get('order_id'))
-
-    order = await ctx.state.get('orders', input.get('order_id'))
-    
-    # This represents a call to some sort of notification service ot indicate that a new order has been placed
-    ctx.logger.info('New order notification sent using Python: ', {
-        'order_id': input.get('order_id'),
-        'order': order,
-        'trace_id': ctx.trace_id
-    })

package/dist/esm/create/templates/basic-tutorial/motia-workbench.json

@@ -1,28 +0,0 @@
-[
-  {
-    "id": "basic-tutorial",
-    "config": {
-      "steps/basic-tutorial/04_new_order_notifications.step.py": {
-        "x": 668,
-        "y": 266,
-        "targetHandlePosition": "left"
-      },
-      "steps/basic-tutorial/03-state-audit-cron.step.ts": {
-        "x": 224,
-        "y": 520
-      },
-      "steps/basic-tutorial/02-process-food-order.step.ts": {
-        "x": 220,
-        "y": 242,
-        "sourceHandlePosition": "right",
-        "targetHandlePosition": "left"
-      },
-      "steps/basic-tutorial/01-api.step.ts": {
-        "x": -243,
-        "y": 199,
-        "sourceHandlePosition": "right",
-        "targetHandlePosition": "left"
-      }
-    }
-  }
-]

package/dist/esm/create/templates/basic-tutorial/services/pet-store.ts.txt

@@ -1,32 +0,0 @@
-export const petStoreService = {
-  createPet: async (pet: { name: string; photoUrl: string }) => {
-    const response = await fetch('https://petstore.swagger.io/v2/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: { id: string; quantity: number; petId: number }) => {
-    const response = await fetch('https://petstore.swagger.io/v2/store/order', {
-      method: 'POST',
-      body: JSON.stringify({
-        id: order.id,
-        quantity: order.quantity,
-        petId: order.petId,
-        shipDate: new Date().toISOString(),
-        status: 'placed',
-      }),
-      headers: {
-        'Content-Type': 'application/json',
-      },
-    })
-    return response.json()
-  },
-}

package/dist/esm/create/templates/default/00-noop.step.ts.txt

@@ -1,33 +0,0 @@
-import { NoopConfig } from 'motia'
-
-/**
- * NOOP Steps don"t hold any logic in code. They are a way
- * to create custom nodes for flows on the workbench and
- * represent external actions such as human in the loop.
- * 
- * In this case, we are using it to add a custom UI 
- * node with a play button to allow you to trigger the first 
- * API step in this flow.
- *
- * For more information, refer to the documentation: https://www.motia.dev/docs/workbench/noop-steps
- */
-export const config: NoopConfig = {
-  type: 'noop',
-  name: 'Flow Starter',
-  description: 'Start the default flow',
-
-  /**
-   * Used mostly to connect nodes that emit to this
-   */
-  virtualSubscribes: [],
-
-  /**
-   * Used mostly to connect nodes that subscribes to this
-   */
-  virtualEmits: ['/default'],
-
-  /**
-   * The flows this step belongs to, will be available in Workbench
-   */
-  flows: ['default'],
-}

package/dist/esm/create/templates/default/00-noop.step.tsx.txt

@@ -1,18 +0,0 @@
-import React from 'react'
-import { BaseNode, NoopNodeProps } from 'motia/workbench'
-import { Button } from '@motiadev/ui'
-
-/**
- * For more information on how to override UI nodes, check documentation https://www.motia.dev/docs/workbench/ui-steps
- */
-export const Node: React.FC<NoopNodeProps> = (data) => {
-  const start = () => {
-    fetch('/default', { method: 'POST', body: JSON.stringify({ message: 'test' }) })
-  }
-
-  return (
-    <BaseNode title="Start" variant="noop" {...data} disableTargetHandle>
-      <Button variant="accent" data-testid="start-flow-button" onClick={start}>Start Flow</Button>
-    </BaseNode>
-  )
-}