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

package/dist/esm/create-step/templates/ui/api.step.txt

@@ -1,20 +0,0 @@
-import React from 'react'
-import { BaseNode, NoopNodeProps } from 'motia/workbench'
-import { Button } from '@motiadev/ui'
-
-export const Node: React.FC<ApiNodeProps> = ({ data }) => {
-  const doSomething = () => {
-    window.alert('Replace this with your custom logic')
-  }
-
-  return (
-    <ApiNode data={{ ...data, description: undefined }}>
-      <div className="flex flex-row gap-4">
-        <div className="flex flex-col items-center text-sm">{data.description}</div>
-        <div className="flex flex-col items-end text-sm">
-          <Button variant="accent" onClick={doSomething}>Play</Button>
-        </div>
-      </div>
-    </ApiNode>
-  )
-}

package/dist/esm/create-step/templates/ui/cron.step.txt

@@ -1,15 +0,0 @@
-import React from 'react'
-import { BaseNode, NoopNodeProps } from 'motia/workbench'
-import { Button } from '@motiadev/ui'
-
-export const Node: React.FC<CronNodeProps> = ({ data }) => {
-  const doSomething = () => {
-    window.alert('Replace this with your custom logic')
-  }
-
-  return (
-    <BaseNode title="{{STEP_NAME}}" variant="noop" {...data} disableTargetHandle>
-      <Button variant="accent" onClick={doSomething}>Click me</Button>
-    </BaseNode>
-  )
-}

package/dist/esm/create-step/templates/ui/event.step.txt

@@ -1,15 +0,0 @@
-import React from 'react'
-import { BaseNode, NoopNodeProps } from 'motia/workbench'
-import { Button } from '@motiadev/ui'
-
-export const Node: React.FC<EventNodeProps> = ({ data }) => {
-  const doSomething = () => {
-    window.alert('Replace this with your custom logic')
-  }
-
-  return (
-    <BaseNode title="{{STEP_NAME}}" variant="noop" {...data} disableTargetHandle>
-      <Button variant="accent" onClick={doSomething}>Click me</Button>
-    </BaseNode>
-  )
-}

package/dist/esm/create-step/templates/ui/noop.step.txt

@@ -1,15 +0,0 @@
-import React from 'react'
-import { BaseNode, NoopNodeProps } from 'motia/workbench'
-import { Button } from '@motiadev/ui'
-
-export const Node: React.FC<NoopNodeProps> = ({ data }) => {
-  const doSomething = () => {
-    window.alert('Replace this with your custom logic')
-  }
-
-  return (
-    <BaseNode title="{{STEP_NAME}}" variant="noop" {...data} disableTargetHandle>
-      <Button variant="accent" onClick={doSomething}>Click me</Button>
-    </BaseNode>
-  )
-}

package/dist/esm/create-step/templates/ui/overrides.d.ts

@@ -1,6 +0,0 @@
-import type { StepAnswers } from '../../types';
-/**
- * Generates a React component override for the step
- */
-export declare function generateOverride(answers: StepAnswers): Promise<string>;
-//# sourceMappingURL=overrides.d.ts.map

package/dist/esm/create-step/templates/ui/overrides.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"overrides.d.ts","sourceRoot":"","sources":["../../../../../src/create-step/templates/ui/overrides.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,aAAa,CAAA;AAE9C;;GAEG;AACH,wBAAsB,gBAAgB,CAAC,OAAO,EAAE,WAAW,GAAG,OAAO,CAAC,MAAM,CAAC,CAgB5E"}

package/dist/esm/create-step/templates/ui/overrides.js

@@ -1,20 +0,0 @@
-import { promises as fs } from 'fs';
-import path from 'path';
-/**
- * Generates a React component override for the step
- */
-export async function generateOverride(answers) {
-    const templatePath = path.join(__dirname, `${answers.type}.step.txt`);
-    const content = await fs.readFile(templatePath, 'utf8');
-    const replacements = {
-        STEP_NAME: answers.name,
-        DESCRIPTION: answers.description || '',
-        TYPE: answers.type,
-        FLOWS: JSON.stringify(answers.flows),
-        EMITS: JSON.stringify(answers.emits),
-    };
-    return Object.entries(replacements).reduce((content, [key, value]) => {
-        const regex = new RegExp(`\\{\\{${key}\\}\\}`, 'g');
-        return content.replace(regex, String(value));
-    }, content);
-}

package/dist/esm/create-step/templates/ui/overrides.ts

@@ -1,24 +0,0 @@
-import { promises as fs } from 'fs'
-import path from 'path'
-import type { StepAnswers } from '../../types'
-
-/**
- * Generates a React component override for the step
- */
-export async function generateOverride(answers: StepAnswers): Promise<string> {
-  const templatePath = path.join(__dirname, `${answers.type}.step.txt`)
-  const content = await fs.readFile(templatePath, 'utf8')
-
-  const replacements: Record<string, string | string[]> = {
-    STEP_NAME: answers.name,
-    DESCRIPTION: answers.description || '',
-    TYPE: answers.type,
-    FLOWS: JSON.stringify(answers.flows),
-    EMITS: JSON.stringify(answers.emits),
-  }
-
-  return Object.entries(replacements).reduce((content, [key, value]) => {
-    const regex = new RegExp(`\\{\\{${key}\\}\\}`, 'g')
-    return content.replace(regex, String(value))
-  }, content)
-}

package/dist/esm/create-step/types.d.ts

@@ -1,22 +0,0 @@
-export declare const STEP_TYPES: readonly ["api", "event", "cron", "noop"];
-export declare const LANGUAGES: readonly ["typescript", "javascript", "python", "ruby"];
-export declare const HTTP_METHODS: readonly ["GET", "POST", "PUT", "DELETE"];
-export type StepType = (typeof STEP_TYPES)[number];
-export type Language = (typeof LANGUAGES)[number];
-export type HttpMethod = (typeof HTTP_METHODS)[number];
-export type StepAnswers = {
-    name: string;
-    language: Language;
-    type: StepType;
-    description?: string;
-    method?: HttpMethod;
-    path?: string;
-    subscriptions?: string[];
-    cronExpression?: string;
-    virtualEmits?: string[];
-    virtualSubscribes?: string[];
-    emits: string[];
-    flows: string[];
-    createOverride: boolean;
-};
-//# sourceMappingURL=types.d.ts.map

package/dist/esm/create-step/types.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../../src/create-step/types.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,UAAU,2CAA4C,CAAA;AACnE,eAAO,MAAM,SAAS,yDAA0D,CAAA;AAChF,eAAO,MAAM,YAAY,2CAA4C,CAAA;AAErE,MAAM,MAAM,QAAQ,GAAG,CAAC,OAAO,UAAU,CAAC,CAAC,MAAM,CAAC,CAAA;AAClD,MAAM,MAAM,QAAQ,GAAG,CAAC,OAAO,SAAS,CAAC,CAAC,MAAM,CAAC,CAAA;AACjD,MAAM,MAAM,UAAU,GAAG,CAAC,OAAO,YAAY,CAAC,CAAC,MAAM,CAAC,CAAA;AAEtD,MAAM,MAAM,WAAW,GAAG;IAExB,IAAI,EAAE,MAAM,CAAA;IACZ,QAAQ,EAAE,QAAQ,CAAA;IAClB,IAAI,EAAE,QAAQ,CAAA;IACd,WAAW,CAAC,EAAE,MAAM,CAAA;IAGpB,MAAM,CAAC,EAAE,UAAU,CAAA;IACnB,IAAI,CAAC,EAAE,MAAM,CAAA;IAGb,aAAa,CAAC,EAAE,MAAM,EAAE,CAAA;IAGxB,cAAc,CAAC,EAAE,MAAM,CAAA;IAGvB,YAAY,CAAC,EAAE,MAAM,EAAE,CAAA;IACvB,iBAAiB,CAAC,EAAE,MAAM,EAAE,CAAA;IAG5B,KAAK,EAAE,MAAM,EAAE,CAAA;IACf,KAAK,EAAE,MAAM,EAAE,CAAA;IACf,cAAc,EAAE,OAAO,CAAA;CACxB,CAAA"}

package/dist/esm/create-step/types.js

@@ -1,3 +0,0 @@
-export const STEP_TYPES = ['api', 'event', 'cron', 'noop'];
-export const LANGUAGES = ['typescript', 'javascript', 'python', 'ruby'];
-export const HTTP_METHODS = ['GET', 'POST', 'PUT', 'DELETE'];

package/dist/esm/create-step/utils.d.ts

@@ -1,3 +0,0 @@
-import type { Language } from './types';
-export declare const getFileExtension: (language: Language) => string;
-//# sourceMappingURL=utils.d.ts.map

package/dist/esm/create-step/utils.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"utils.d.ts","sourceRoot":"","sources":["../../../src/create-step/utils.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAA;AAEvC,eAAO,MAAM,gBAAgB,GAAI,UAAU,QAAQ,KAAG,MASrD,CAAA"}

package/dist/esm/create-step/utils.js

@@ -1,9 +0,0 @@
-export const getFileExtension = (language) => {
-    const extensions = {
-        typescript: '.ts',
-        javascript: '.js',
-        python: '.py',
-        ruby: '.rb',
-    };
-    return extensions[language];
-};

package/dist/esm/cursor-rules/dot-files/.claude/agents/motia-developer.md

@@ -1,95 +0,0 @@
----
-name: motia-developer
-description: Expert Motia developer. Use PROACTIVELY for all Motia development tasks. References comprehensive cursor rules for patterns and best practices.
-tools: Read, Edit, Write, Grep, Bash
-model: inherit
----
-
-You are an expert Motia developer with comprehensive knowledge of all Motia patterns.
-
-## CRITICAL: Always Read Cursor Rules First
-
-Before writing ANY Motia code, you MUST read the relevant cursor rules from `.cursor/rules/`:
-
-### Step Type Guides (in `.cursor/rules/motia/`)
-
-1. **`api-steps.mdc`** - HTTP endpoints
-   - Creating API Steps with TypeScript, JavaScript, or Python
-   - Request/response schemas, validation, middleware
-   - When to emit events vs process directly
-
-2. **`event-steps.mdc`** - Background tasks
-   - Creating Event Steps with TypeScript, JavaScript, or Python
-   - Topic subscription, event chaining, retry mechanisms
-   - Asynchronous workflow patterns
-
-3. **`cron-steps.mdc`** - Scheduled tasks
-   - Creating Cron Steps with TypeScript, JavaScript, or Python
-   - Cron expression syntax, idempotent patterns
-   - When to emit events from scheduled jobs
-
-4. **`state-management.mdc`** - State/cache management
-   - Using state across steps with TypeScript, JavaScript, or Python
-   - When to use state vs database
-   - TTL configuration, caching strategies
-
-5. **`middlewares.mdc`** - Request/response middleware
-   - Creating middleware with TypeScript, JavaScript, or Python
-   - Authentication, validation, error handling
-   - Middleware composition patterns
-
-6. **`realtime-streaming.mdc`** - Real-time data
-   - Server-Sent Events (SSE) patterns
-   - WebSocket support
-   - Stream configuration and usage
-
-7. **`virtual-steps.mdc`** - Visual flow connections
-   - Creating NOOP steps for Workbench
-   - Virtual emits/subscribes for documentation
-   - Workflow visualization
-
-8. **`ui-steps.mdc`** - Custom Workbench components
-   - Creating custom visual components (TypeScript/React)
-   - EventNode, ApiNode, CronNode components
-   - Styling with Tailwind
-
-### Architecture Guides (in `.cursor/architecture/`)
-
-9. **`architecture.mdc`** - Project structure
-   - File organization, naming conventions
-   - Domain-Driven Design patterns
-   - Services, repositories, utilities structure
-
-10. **`error-handling.mdc`** - Error handling
-    - Custom error classes
-    - Middleware error handling
-    - ZodError/Pydantic validation errors
-
-## Workflow
-
-1. **Identify the task type** (API, Event, Cron, etc.)
-2. **Read the relevant cursor rule(s)** from the list above
-3. **Follow the patterns exactly** as shown in the guide
-4. **Generate types** after config changes:
-   ```bash
-   npx motia generate-types
-   ```
-
-## Key Principles
-
-- **All guides have TypeScript, JavaScript, and Python examples**
-- **Always export `config` and `handler`**
-- **List all emits in config before using them**
-- **Follow naming conventions**: `*.step.ts` (TS), `*.step.js` (JS), `*_step.py` (Python)
-- **Use Domain-Driven Design**: Steps → Services → Repositories
-
-## Never Guess
-
-If you're unsure about any Motia pattern:
-1. Read the relevant cursor rule from the list above
-2. Check existing steps in the project
-3. Follow the examples in the guides exactly
-
----
-
-Remember: The 10 cursor rules in `.cursor/rules/` are your source of truth. Always read them first.

package/dist/esm/cursor-rules/dot-files/.cursor/architecture/architecture.mdc

@@ -1,96 +0,0 @@
----
-description: How to structure your Motia project
-globs:
-alwaysApply: true
----
-
-# Architecture Guide
-
-## Overview
-
-This guide covers the architecture of a Motia project.
-
-## File Structure
-
-All step files should be underneath the `steps/` folder.
-
-Underneath the `steps/` folder, create subfolders for Flows. Flows are used to group steps together.
-
-## Step Naming Conventions
-
-### Typescript
-
-- Use kebab-case for filenames: `resource-processing.step.ts`
-- Include `.step` before language extension
-
-### Python
-
-- Use snake_case for filenames: `data_processor_step.py`
-- Include `_step` before language extension
-
-### Global
-
-- Match handler names to config names
-- Use descriptive, action-oriented names
-
-## Code Style Guidelines
-
-- **JavaScript**: Use modern ES6+ features, async/await, proper error handling
-- **TypeScript**: Make sure you use the correct Handlers type that is auto generated on the `types.d.ts` file.
-
-## Defining Middlewares
-
-Middleware is a powerful feature in Motia to help adding common validation, error
-handling and other common logic to your steps.
-
-- Make sure to add all the middlewares in a single folder, called `middlewares/`.
-- Create a comprehensive file name for the middleware, like `auth.middleware.ts`.
-- Follow SOLID principles with separation of concerns in middlewares, create a middleware for each responsibility.
-- Use core middleware to handle ZodError gracefully (see [Error Handling Guide](./error-handling.mdc))
-- Rate limiting and CORS are not needed to be handled in middleware since they're an infrastructure concern.
-
-## Domain Driven Design
-
-Make sure you follow Domain Driven Design principles in your project.
-
-- Create `/src/services` folder to store your services, this is where it holds business logic.
-- Create `/src/repositories` folder to store your repositories, this is where it holds data access logic.
-- Create `/src/utils` folder to store your utility functions.
-- Models and DTOs are not quite necessary, we can rely on zod to create the models and DTOs from the steps.
-- Controller layer is the Steps, it should have mostly logic around validation and calling services.
-- Avoid having Service methods with just a call to the Repository, it should have some logic around it, if it doesn't have, then Steps can have access to repositories directly.
-
-### Services
-
-Defining services can be done in the following way:
-
-- Create a folder underneath `/src/services/` folder, like `/src/services/auth/`.
-- Create a file inside the folder called `index.ts`.
-- Inside `index.ts`, export a constant with the name of the service, with the methods as properties.
-- Methods should be defined as separate files, use export named functions.
-- Use the service in the Steps.
-
-#### Example
-
-```typescript
-/**
- * Business logic for authentication defined in a separate file in the same folder.
- */
-import { login } from './login'
-
-/**
- * Constant with the name of the service, with the methods as properties.
- */
-export const authService = {
-  login
-}
-```
-
-## Logging and observability
-
-- Make sure to use the Logger from Motia (from context object) to log messages.
-- Make sure to have visibility of what is going on in a request
-- Before throwing errors, make sure to log the issue, identify if issue is a validation blocker, then log with `logger.warn`, if it's something that is not supposed to happen, then log with `logger.error`.
-- Make sure to add context to the logs to help identify any potential issues.
-
-

package/dist/esm/cursor-rules/dot-files/.cursor/architecture/error-handling.mdc

@@ -1,122 +0,0 @@
----
-description: How to handle errors in a Motia project
-globs:
-alwaysApply: true
----
-
-# Error Handling Guide
-
-Errors happen, but we need to handle them gracefully. Make sure you create a custom error class for your project, underneath `/src/errors/` folder.
-
-## Good practices
-
-- Use Custom error to return errors to the client.
-- Anything that is not the error class, should be logged with `logger.error`. And root cause should be omitted to the client.
-
-## Create a custom Error class
-
-Name: `/src/errors/base.error.ts`
-
-```typescript
-export class BaseError extends Error {
-  public readonly status: number
-  public readonly code: string
-  public readonly metadata: Record<string, any>
-
-  constructor(
-    message: string,
-    status: number = 500,
-    code: string = 'INTERNAL_SERVER_ERROR',
-    metadata: Record<string, any> = {}
-  ) {
-    super(message)
-    this.name = this.constructor.name
-    this.status = status
-    this.code = code
-    this.metadata = metadata
-
-    // Maintains proper stack trace for where our error was thrown
-    Error.captureStackTrace(this, this.constructor)
-  }
-
-  toJSON() {
-    return {
-      error: {
-        name: this.name,
-        message: this.message,
-        code: this.code,
-        status: this.status,
-        ...(Object.keys(this.metadata).length > 0 && { metadata: this.metadata }),
-      },
-    }
-  }
-}
-```
-
-Then create sub class for specific errors that are commonly thrown in your project.
-
-Name: `/src/errors/not-found.error.ts`
-
-```typescript
-import { BaseError } from './base.error'
-
-export class NotFoundError extends BaseError {
-  constructor(message: string = 'Not Found', metadata: Record<string, any> = {}) {
-    super(message, 404, 'NOT_FOUND', metadata)
-  }
-}
-```
-
-## Core Middleware
-
-Make sure you create a core middleware that will be added to ALL API Steps.
-
-File: `/src/middlewares/core.middleware.ts`
-
-```typescript
-import { ApiMiddleware } from 'motia'
-import { ZodError } from 'zod'
-import { BaseError } from '../errors/base.error'
-
-export const coreMiddleware: ApiMiddleware = async (req, ctx, next) => {
-  const logger = ctx.logger
-
-  try {
-    return await next()
-  } catch (error: any) {
-    if (error instanceof ZodError) {
-      logger.error('Validation error', {
-        error,
-        stack: error.stack,
-        errors: error.errors,
-      })
-
-      return {
-        status: 400,
-        body: {
-          error: 'Invalid request body',
-          data: error.errors,
-        },
-      }
-    } else if (error instanceof BaseError) {
-      logger.error('BaseError', {
-        status: error.status,
-        code: error.code,
-        metadata: error.metadata,
-        name: error.name,
-        message: error.message,
-      })
-
-      return { status: error.status, body: error.toJSON() }
-    }
-
-    logger.error('Error while performing request', {
-      error,
-      body: req.body,
-      stack: error.stack,
-    })
-
-    return { status: 500, body: { error: 'Internal Server Error' } }
-  }
-}
-```

package/dist/esm/cursor-rules/dot-files/.cursor/index.mdc

@@ -1,34 +0,0 @@
----
-description: Rules for the project
-globs:
-alwaysApply: true
----
-
-## Real time events
-
-Make sure to use [real time events guide](./rules/motia/realtime-streaming.mdc) to create a new real time event.
-
-## State/Cache management
-
-Make sure to use [state management guide](./rules/motia/state-management.mdc) to create a new state management.
-
-## Creating HTTP Endpoints
-
-Make sure to use [API steps guide](./rules/motia/api-steps.mdc) to create new HTTP endpoints.
-
-## Background Tasks
-
-Make sure to use [event steps guide](./rules/motia/event-steps.mdc) to create new background tasks.
-
-## Scheduled Tasks
-
-Make sure to use [cron steps guide](./rules/motia/cron-steps.mdc) to create new scheduled tasks.
-
-## Virtual Steps & Flow Visualization
-
-Make sure to use [virtual steps guide](./rules/motia/virtual-steps.mdc) when connecting nodes virtually and creating smooth flows in Workbench.
-
-## Authentication
-
-If ever need to add authentication, make sure to use middleware to authenticate the request.
-Make sure to use [middlewares](./rules/motia/middlewares.mdc) to validate the requests.