npm - motia - Versions diffs - 0.17.11-beta.193 → 0.17.12-beta.194 - Mend

motia 0.17.11-beta.193 → 0.17.12-beta.194

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (37) hide show

package/README.md CHANGED Viewed

@@ -46,7 +46,7 @@ Follow the prompts to pick a template, project name, and language.
 Inside your new project folder, launch the dev server:
 ```bash
-npx motia dev # ➜ http://localhost:3000
+npm run dev # ➜ http://localhost:3000
 ```
 This spins up the Motia Workbench – a local UI for building, testing & observing your backend in real-time.
@@ -245,8 +245,6 @@ npm run dev [options]
 yarn dev [options]
 # or
 pnpm dev [options]
-# or
-bun run dev  [options]
 # options:
   # -p, --port <port>     The port to run the server on (default: 3000)

package/dist/create/templates/hello/.env ADDED Viewed

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello/README.md.txt CHANGED Viewed

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
-A Motia project created with the starter template.
+This is a **Motia** project bootstrapped with the Motia CLI.
-## 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**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 ## Quick Start
@@ -17,67 +15,19 @@ yarn dev
 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).
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-## 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
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+You can start editing the project by making changes to `src/hello/hello-api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
-## Project Structure
-```
-steps/              # Your Step definitions (or use src/)
-motia.config.ts     # Motia configuration
-```
+## Project Config
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 ## 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
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](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's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/hello_js/.env ADDED Viewed

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello_js/README.md.txt CHANGED Viewed

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
-A Motia project created with the starter template.
+This is a **Motia** project bootstrapped with the Motia CLI.
-## 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**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 ## Quick Start
@@ -17,67 +15,19 @@ yarn dev
 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).
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-## 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
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+You can start editing the project by making changes to `src/hello/hello-api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
-## Project Structure
-```
-steps/              # Your Step definitions (or use src/)
-motia.config.ts     # Motia configuration
-```
+## Project Config
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 ## 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
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](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's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/hello_multilang/.env ADDED Viewed

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello_multilang/README.md.txt CHANGED Viewed

@@ -1,20 +1,8 @@
 # {{PROJECT_NAME}}
-A Motia project created with the **multi-language** starter template (TypeScript + Python).
+This is a **Motia** project bootstrapped with the Motia CLI.
-## 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**.
-## Polyglot Architecture
-This template demonstrates Motia's polyglot capabilities by combining:
-- **TypeScript**: API endpoint (`hello-api.step.ts`) - handles HTTP requests
-- **Python**: Event processor (`process_greeting_step.py`) - handles background processing
-- **JavaScript**: Logger (`log-greeting.step.js`) - handles workflow completion
-This shows how you can use the best language for each task while keeping everything in a single unified system.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 ## Quick Start
@@ -27,80 +15,19 @@ yarn dev
 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).
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-## How It Works
-1. **TypeScript API Step** receives the HTTP request at `/hello`
-2. It emits a `process-greeting` event with the request data
-3. **Python Event Step** picks up the event, processes it, and stores the result in state
-4. Python emits a `greeting-processed` event
-5. **JavaScript Event Step** logs the completed workflow
-## 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
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+You can start editing the project by making changes to `src/hello/hello-api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
-## Project Structure
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
-```
-steps/                           # Your Step definitions
-├── hello/
-│   ├── hello-api.step.ts       # TypeScript API endpoint
-│   ├── process_greeting_step.py # Python event processor
-│   └── log-greeting.step.js    # JavaScript logger
-motia.config.ts                  # Motia configuration
-requirements.txt                 # Python dependencies
-```
+## Project Config
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 ## 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
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](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's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/hello_python/.env ADDED Viewed

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello_python/README.md.txt CHANGED Viewed

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
-A Motia project created with the starter template.
+This is a **Motia** project bootstrapped with the Motia CLI.
-## 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**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 ## Quick Start
@@ -17,68 +15,19 @@ yarn dev
 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).
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-## 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
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+You can start editing the project by making changes to `src/hello/hello_api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
-## Project Structure
-```
-steps/              # Your Step definitions (or use src/)
-motia.config.ts     # Motia configuration
-requirements.txt    # Python dependencies
-```
+## Project Config
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required. You can write Steps in Python, TypeScript, or JavaScript, all in the same project.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 ## 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
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](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's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/nodejs/.env ADDED Viewed

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+API_URL="https://xnigaj-xtnawg.motiahub.com"
+SAMPLE_EMAIL="test@test.com"

package/dist/create/templates/nodejs/README.md.txt CHANGED Viewed

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
-A Motia tutorial project in TypeScript.
+This is a **Motia** project bootstrapped with the Motia CLI.
-## 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**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 ## Quick Start
@@ -17,76 +15,19 @@ yarn dev
 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
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-```
-steps/              # Your Step definitions (or use src/)
-src/                # Shared services and utilities
-motia.config.ts     # Motia configuration
-```
+You can start editing the project by making changes to `src/petstore/api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
-## Tutorial
+## Project Config
-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
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 ## 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
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](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's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/nodejs/src/petstore/api.step.ts.txt CHANGED Viewed

@@ -38,7 +38,7 @@ export const handler: Handlers['ApiTrigger'] = async (req, { logger, traceId, em
       topic: 'process-food-order',
       data: {
         quantity: foodOrder.quantity,
-        email: 'test@test.com', // sample email
+        email: process.env.SAMPLE_EMAIL || 'test@test.com',
         petId: newPetRecord.id,
       },
     })

package/dist/create/templates/nodejs/src/petstore/state-audit-cron.step.ts.txt CHANGED Viewed

@@ -28,7 +28,7 @@ export const handler: Handlers['StateAuditJob'] = async ({ logger, state, emit }
       await emit({
         topic: 'notification',
         data: {
-          email: 'test@test.com',
+          email: process.env.SAMPLE_EMAIL || 'test@test.com',
           templateId: 'order-audit-warning',
           templateData: {
             orderId: item.id,

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

@@ -1,8 +1,10 @@
 import type { Order, Pet } from './types'
+const API_URL = process.env.API_URL || 'https://xnigaj-xtnawg.motiahub.com'
 export const petStoreService = {
   createPet: async (pet: Omit<Pet, 'id'>): Promise<Pet> => {
-    const response = await fetch('https://xnigaj-xtnawg.motiahub.com/pet', {
+    const response = await fetch(`${API_URL}/pet`, {
       method: 'POST',
       body: JSON.stringify({
         name: pet?.name ?? '',
@@ -14,7 +16,7 @@ export const petStoreService = {
     return response.json()
   },
   createOrder: async (order: Omit<Order, 'id' | 'complete'>): Promise<Order> => {
-    const response = await fetch('https://xnigaj-xtnawg.motiahub.com/store/order', {
+    const response = await fetch(`${API_URL}/store/order`, {
       method: 'POST',
       body: JSON.stringify({
         quantity: order?.quantity ?? 1,

package/dist/create/templates/python/.env ADDED Viewed

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+API_URL="https://xnigaj-xtnawg.motiahub.com"
+SAMPLE_EMAIL="test@test.com"

package/dist/create/templates/python/README.md.txt CHANGED Viewed

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
-A Motia tutorial project in Python.
+This is a **Motia** project bootstrapped with the Motia CLI.
-## 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**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 ## Quick Start
@@ -17,77 +15,19 @@ yarn dev
 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
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-```
-steps/              # Your Step definitions (or use src/)
-src/                 # Shared services and utilities
-motia.config.ts      # Motia configuration
-requirements.txt     # Python dependencies
-```
+You can start editing the project by making changes to `src/petstore/api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required. You can write Steps in Python, TypeScript, or JavaScript, all in the same project.
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
-## Tutorial
+## Project Config
-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
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 ## 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
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](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's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/python/src/petstore/api_step.py.txt CHANGED Viewed

@@ -1,3 +1,4 @@
+import os
 from pydantic import BaseModel
 from typing import Optional
 from src.services.pet_store import pet_store_service
@@ -42,7 +43,7 @@ async def handler(req, context):
             "topic": "process-food-order",
             "data": {
                 "quantity": food_order.get("quantity"),
-                "email": "test@test.com",  # sample email
+                "email": os.environ.get("SAMPLE_EMAIL", "test@test.com"),
                 "pet_id": new_pet_record.get("id"),
             },
         })

package/dist/create/templates/python/src/petstore/state_audit_cron_step.py.txt CHANGED Viewed

@@ -1,3 +1,4 @@
+import os
 from datetime import datetime, timezone
 config = {
@@ -27,7 +28,7 @@ async def handler(context):
             await context.emit({
                 "topic": "notification",
                 "data": {
-                    "email": "test@test.com",
+                    "email": os.environ.get("SAMPLE_EMAIL", "test@test.com"),
                     "template_id": "order-audit-warning",
                     "template_data": {
                         "order_id": item.get("id"),

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

@@ -1,7 +1,10 @@
+import os
 import httpx
 from typing import Dict, Any
 from .types import Order, Pet
+api_url = os.environ.get("API_URL", "https://xnigaj-xtnawg.motiahub.com")
 class PetStoreService:
     async def create_pet(self, pet: Dict[str, Any]) -> Pet:
         pet_data = {
@@ -12,7 +15,7 @@ class PetStoreService:
         async with httpx.AsyncClient() as client:
             response = await client.post(
-                'https://xnigaj-xtnawg.motiahub.com/pet',
+                f"{api_url}/pet",
                 json=pet_data,
                 headers={'Content-Type': 'application/json'}
             )
@@ -28,7 +31,7 @@ class PetStoreService:
             }
             response = await client.post(
-                'https://xnigaj-xtnawg.motiahub.com/store/order',
+                f"{api_url}/store/order",
                 json=order_data,
                 headers={'Content-Type': 'application/json'}
             )

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

@@ -3,48 +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-29"]
+    "lines": ["7-30"]
   },
   {
     "id": "api-configuration",
     "title": "API Step",
     "description": "Definition of an API endpoint",
-    "lines": ["18", "22-23"]
+    "lines": ["19", "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-15", "24"]
+    "lines": ["7-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", "25-27"]
+    "lines": ["5", "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": ["28", "41-48"]
+    "lines": ["29", "42-49"]
   },
   {
     "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-50"]
+    "lines": ["32-51"]
   },
   {
     "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": ["33"]
+    "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": ["50"]
+    "lines": ["51"]
   }
 ]

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

@@ -3,24 +3,18 @@
     "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"
-    ]
+    "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": [
-      "12-39"
-    ]
+    "lines": ["13-40"]
   }
-]
+]

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

@@ -86,7 +86,7 @@ Before writing ANY Motia code, you MUST read the relevant cursor rules from `.cu
 ## Key Principles
 - **All guides have TypeScript, JavaScript, and Python examples**
-- **Steps can live in `/src` or `/steps`** - Motia discovers both (use `/src` for modern structure)
+- **Steps can live anywhere within `/src`** - Motia discovers them automatically
 - **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)

package/dist/cursor-rules/dot-files/.cursor/architecture/architecture.mdc CHANGED Viewed

@@ -10,17 +10,13 @@ alwaysApply: true
 This guide covers the architecture and best practices for structuring Motia projects.
-**Key Takeaway**: Motia automatically discovers steps from anywhere in your project. Modern projects use `/src` for a familiar structure that works seamlessly with Domain-Driven Design.
+**Key Takeaway**: Motia automatically discovers steps from anywhere in the `/src` folder. Modern projects use `/src` for a familiar structure that works seamlessly with Domain-Driven Design.
 ## File Structure
-Motia automatically discovers step files from your project. You can organize steps in either:
+Motia automatically discovers step files from your project.
-- **`/src` folder** (recommended) - Familiar pattern for most developers
-- **`/steps` folder** - Traditional Motia pattern
-- Both folders simultaneously
-### Recommended Structure (using `/src`)
+### Recommended Structure
 ```
 project/
@@ -39,24 +35,7 @@ project/
 └── motia.config.ts
 ```
-### Alternative Structure (using `/steps`)
-```
-project/
-├── steps/
-│   ├── api/
-│   │   └── users.step.ts
-│   ├── events/
-│   │   └── order-processing.step.ts
-│   └── cron/
-│       └── cleanup.step.ts
-├── src/
-│   ├── services/
-│   └── utils/
-└── motia.config.ts
-```
-Create subfolders within your chosen directory to organize related steps into logical groups (domains, features, or flows).
+Create subfolders within your `/src` directory to organize related steps into logical groups (domains, features, or flows).
 **Why `/src` is recommended:**
 - Familiar to developers from other frameworks (Next.js, NestJS, etc.)
@@ -109,7 +88,7 @@ Motia encourages Domain-Driven Design (DDD) principles for maintainable, scalabl
 ### Folder Structure for DDD
-When using `/src` for steps (recommended), your structure naturally supports DDD:
+When using `/src` for steps, your structure naturally supports DDD:
 ```
 src/

package/dist/cursor-rules/dot-files/.cursor/rules/motia/api-steps.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: How to create HTTP endpoints in Motia
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 # API Steps Guide
@@ -9,7 +9,7 @@ API Steps expose HTTP endpoints that can trigger workflows and emit events.
 ## Creating API Steps
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively.
 - Steps in Python should end with `_step.py`.

package/dist/cursor-rules/dot-files/.cursor/rules/motia/cron-steps.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: Cron Steps are scheduled tasks that run based on cron expressions.
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 # Cron Steps Guide
@@ -15,7 +15,7 @@ ultimately trigger an Event Step that will handle the logic.
 ## Creating Cron Steps
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively
 - Steps in Python should end with `_step.py`

package/dist/cursor-rules/dot-files/.cursor/rules/motia/event-steps.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: How to create background tasks in Motia
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 # Event Steps Guide
@@ -19,7 +19,7 @@ Other applicable examples are tasks that are likely to fail, examples:
 ## Creating Event Steps
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively.
 - Steps in Python should end with `_step.py`.

package/dist/cursor-rules/dot-files/.cursor/rules/motia/middlewares.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: Middlewares are used to execute code before and after the handler is called
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py,middlewares/**/*.middleware.ts,middlewares/**/*.middleware.js,middlewares/**/*_middleware.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py,middlewares/**/*.middleware.ts,middlewares/**/*.middleware.js,middlewares/**/*_middleware.py
 alwaysApply: false
 ---
 # Middlewares Guide

package/dist/cursor-rules/dot-files/.cursor/rules/motia/motia-config.mdc CHANGED Viewed

@@ -196,7 +196,7 @@ export default config({
 **Project structure:**
 ```
 project/
-├── src/              # Steps can be in /src or /steps
+├── src/              # Steps can be placed anywhere within /src
 │   └── api/
 │       └── example.step.ts
 ├── plugins/

package/dist/cursor-rules/dot-files/.cursor/rules/motia/realtime-streaming.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: Real-time streaming
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py,steps/**/*.stream.ts,steps/**/*.stream.js,steps/**/*_stream.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py,src/**/*.stream.ts,src/**/*.stream.js,src/**/*_stream.py
 alwaysApply: false
 ---
 # Real-time Streaming
@@ -56,7 +56,7 @@ export interface StreamConfig {
 ### TypeScript Example
 ```typescript
-// steps/streams/chat-messages.stream.ts
+// src/streams/chat-messages.stream.ts
 import { StreamConfig } from 'motia'
 import { z } from 'zod'
@@ -81,7 +81,7 @@ export const config: StreamConfig = {
 #### With Pydantic (Optional)
 ```python
-# steps/streams/chat_messages_stream.py
+# src/streams/chat_messages_stream.py
 from pydantic import BaseModel
 class ChatMessage(BaseModel):
@@ -100,7 +100,7 @@ config = {
 #### Without Pydantic (Pure JSON Schema)
 ```python
-# steps/streams/chat_messages_stream.py
+# src/streams/chat_messages_stream.py
 config = {
     "name": "chatMessage",

package/dist/cursor-rules/dot-files/.cursor/rules/motia/state-management.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: Managing state across Steps
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---

package/dist/cursor-rules/dot-files/.cursor/rules/motia/ui-steps.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: Overriding the UI of Steps in Motia
-globs: steps/**/*.step.tsx,steps/**/*.step.jsx,steps/**/*_step.tsx,steps/**/*_step.jsx
+globs: src/**/*.step.tsx,src/**/*.step.jsx,src/**/*_step.tsx,src/**/*_step.jsx
 alwaysApply: true
 ---
@@ -15,7 +15,7 @@ With UI Steps, you can enhance the user experience by designing intuitive, conte
 To create a custom UI for a step, create a .tsx or .jsx file next to your step file with the same base name:
 ```
-steps/
+src/
 └── myStep/
   ├── myStep.step.ts      # Step definition
   └── myStep.step.tsx     # Visual override

package/dist/cursor-rules/dot-files/.cursor/rules/motia/virtual-steps.mdc CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 description: Connecting nodes virtually and creating a smooth flow in Workbench
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
@@ -15,7 +15,7 @@ or without NOOP Steps.
 ## Creating NOOP Steps
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively.
 - Steps in Python should end with `_step.py`.

package/dist/cursor-rules/dot-files/AGENTS.md CHANGED Viewed

@@ -63,9 +63,9 @@ Architecture guides in `.cursor/architecture/`:
 ### Project Structure
-Motia discovers steps from both `/src` and `/steps` folders. Modern projects typically use `/src`:
+Motia discovers steps from the `/src` folder:
-**Recommended Structure (using `/src`):**
+**Recommended Structure:**
 ```
 project/
 ├── .cursor/rules/   # DETAILED GUIDES - Read these first!
@@ -88,19 +88,6 @@ project/
 └── types.d.ts      # Auto-generated types
 ```
-**Alternative Structure (using `/steps`):**
-```
-project/
-├── steps/          # Step definitions
-│   ├── api/
-│   ├── events/
-│   └── cron/
-├── src/
-│   ├── services/
-│   └── utils/
-└── motia.config.ts
-```
 ### Step Naming Conventions
 **TypeScript/JavaScript:** `my-step.step.ts` (kebab-case)

package/dist/cursor-rules/dot-files/CLAUDE.md CHANGED Viewed

@@ -48,7 +48,7 @@ All guides in `.cursor/rules/` with **TypeScript, JavaScript, and Python** examp
 See `AGENTS.md` in this directory for a quick overview and links to specific guides.
-**Important**: Motia discovers steps from both `/src` and `/steps` folders. Modern projects use `/src` for a familiar structure.
+**Important**: Motia discovers steps from the `/src` folder.
 ## Key Commands

package/dist/install.mjs CHANGED Viewed

@@ -2,13 +2,13 @@ import { getStepFiles, getStreamFiles } from "./generate-locked-data.mjs";
 import { internalLogger } from "./utils/internal-logger.mjs";
 import { executeCommand } from "./utils/execute-command.mjs";
 import { getPythonCommand } from "./utils/python-version-utils.mjs";
-import { activatePythonVenv } from "./utils/activate-python-env.mjs";
+import { activatePythonVenv, getSitePackagesPath } from "./utils/activate-python-env.mjs";
 import { getInstallCommand } from "./utils/validate-python-environment.mjs";
 import { ensureUvInstalled } from "./utils/ensure-uv.mjs";
 import { installLambdaPythonPackages } from "./utils/install-lambda-python-packages.mjs";
-import fs from "fs";
-import path from "path";
 import pc from "picocolors";
+import fs from "node:fs";
+import path from "node:path";
 //#region src/install.ts
 const pythonInstall = async ({ baseDir, isVerbose = false, pythonVersion = "3.13" }) => {
@@ -22,9 +22,21 @@ const pythonInstall = async ({ baseDir, isVerbose = false, pythonVersion = "3.13
 	try {
 		const pythonCmd = await getPythonCommand(pythonVersion, baseDir);
 		if (isVerbose) console.log(`🐍 Using Python command: ${pythonCmd}`);
-		if (!fs.existsSync(venvPath)) {
-			console.log("📦 Creating Python virtual environment...");
-			await executeCommand(`${pythonCmd} -m venv python_modules`, baseDir);
+		if (fs.existsSync(venvPath)) fs.rmSync(venvPath, {
+			recursive: true,
+			force: true
+		});
+		console.log("📦 Creating Python virtual environment...");
+		await executeCommand(`${pythonCmd} -m venv python_modules`, baseDir);
+		const sitePackagesPath = getSitePackagesPath({
+			baseDir,
+			pythonVersion
+		});
+		if (!sitePackagesPath || !fs.existsSync(sitePackagesPath)) {
+			const installCmd = getInstallCommand(baseDir);
+			internalLogger.error("Python virtual environment was not created");
+			internalLogger.info(`Please try running ${pc.cyan(installCmd)} or manually create the venv with: ${pc.cyan("python3 -m venv python_modules")}`);
+			process.exit(1);
 		}
 		activatePythonVenv({
 			baseDir,
@@ -43,13 +55,6 @@ const pythonInstall = async ({ baseDir, isVerbose = false, pythonVersion = "3.13
 			if (isVerbose) console.log("📄 Using requirements from:", requirement);
 			await executeCommand(`pip install -r "${requirement}" --only-binary=:all:`, baseDir);
 		}
-		const sitePackagesPath = process.env.PYTHON_SITE_PACKAGES;
-		if (!sitePackagesPath || !fs.existsSync(sitePackagesPath)) {
-			const installCmd = getInstallCommand(baseDir);
-			internalLogger.error("Python virtual environment was not created");
-			internalLogger.info(`Please try running ${pc.cyan(installCmd)} or manually create the venv with: ${pc.cyan("python3 -m venv python_modules")}`);
-			process.exit(1);
-		}
 	} catch (error) {
 		const errorMessage = error instanceof Error ? error.message : String(error);
 		internalLogger.error("Installation failed:", errorMessage);

package/dist/install.mjs.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"install.mjs","names":[],"sources":["../src/install.ts"],"sourcesContent":["import fs from 'fs'\nimport path from 'path'\nimport pc from 'picocolors'\nimport { getStepFiles, getStreamFiles } from './generate-locked-data'\nimport { activatePythonVenv } from './utils/activate-python-env'\nimport { ensureUvInstalled } from './utils/ensure-uv'\nimport { executeCommand } from './utils/execute-command'\nimport { installLambdaPythonPackages } from './utils/install-lambda-python-packages'\nimport { internalLogger } from './utils/internal-logger'\nimport { getPythonCommand } from './utils/python-version-utils'\nimport { getInstallCommand } from './utils/validate-python-environment'\n\ninterface InstallConfig {\n isVerbose?: boolean\n pythonVersion?: string\n}\n\ntype PythonInstallConfig = InstallConfig & { baseDir: string }\n\nexport const pythonInstall = async ({\n baseDir,\n isVerbose = false,\n pythonVersion = '3.13',\n}: PythonInstallConfig): Promise<void> => {\n const venvPath = path.join(baseDir, 'python_modules')\n console.log('📦 Installing Python dependencies...', venvPath)\n\n const coreRequirementsPath = path.join(baseDir, 'node_modules', 'motia', 'dist', 'requirements-core.txt')\n const snapRequirementsPath = path.join(baseDir, 'node_modules', 'motia', 'dist', 'requirements-snap.txt')\n const localRequirements = path.join(baseDir, 'requirements.txt')\n\n const requirementsList = [coreRequirementsPath, snapRequirementsPath, localRequirements]\n\n try {\n // Get the appropriate Python command\n const pythonCmd = await getPythonCommand(pythonVersion, baseDir)\n if (isVerbose) {\n console.log(`🐍 Using Python command: ${pythonCmd}`)\n }\n\n // Check if virtual environment exists\n if (!fs.existsSync(venvPath)) {\n console.log('📦 Creating Python virtual environment...')\n await executeCommand(`${pythonCmd} -m venv python_modules`, baseDir)\n }\n\n activatePythonVenv({ baseDir, isVerbose, pythonVersion })\n\n // Ensure UV is installed\n console.log('🔧 Checking UV installation...')\n await ensureUvInstalled()\n console.log('✅ UV is available')\n\n installLambdaPythonPackages({ isVerbose, requirementsList })\n\n // Install requirements\n console.log('📥 Installing Python dependencies...')\n\n // Core requirements\n\n for (const requirement of requirementsList) {\n if (fs.existsSync(requirement)) {\n if (isVerbose) {\n console.log('📄 Using requirements from:', requirement)\n }\n await executeCommand(`pip install -r \"${requirement}\" --only-binary=:all:`, baseDir)\n }\n }\n\n const sitePackagesPath = process.env.PYTHON_SITE_PACKAGES\n\n if (!sitePackagesPath \|\| !fs.existsSync(sitePackagesPath)) {\n const installCmd = getInstallCommand(baseDir)\n internalLogger.error('Python virtual environment was not created')\n internalLogger.info(\n `Please try running ${pc.cyan(installCmd)} or manually create the venv with: ${pc.cyan('python3 -m venv python_modules')}`,\n )\n process.exit(1)\n }\n } catch (error) {\n const errorMessage = error instanceof Error ? error.message : String(error)\n internalLogger.error('Installation failed:', errorMessage)\n process.exit(1)\n }\n}\n\nexport const install = async ({ isVerbose = false, pythonVersion = '3.13' }: InstallConfig): Promise<void> => {\n const baseDir = process.cwd()\n\n const steps = getStepFiles(baseDir)\n const streams = getStreamFiles(baseDir)\n if (steps.some((file) => file.endsWith('.py')) \|\| streams.some((file) => file.endsWith('.py'))) {\n await pythonInstall({ baseDir, isVerbose, pythonVersion })\n }\n\n console.info('✅ Installation completed successfully!')\n\n process.exit(0)\n}\n"],"mappings":";;;;;;;;;;;;;AAmBA,MAAa,gBAAgB,OAAO,EAClC,SACA,YAAY,OACZ,gBAAgB,aACwB;CACxC,MAAM,WAAW,KAAK,KAAK,SAAS,iBAAiB;AACrD,SAAQ,IAAI,wCAAwC,SAAS;CAM7D,MAAM,mBAAmB;EAJI,KAAK,KAAK,SAAS,gBAAgB,SAAS,QAAQ,wBAAwB;EAC5E,KAAK,KAAK,SAAS,gBAAgB,SAAS,QAAQ,wBAAwB;EAC/E,KAAK,KAAK,SAAS,mBAAmB;EAEwB;AAExF,KAAI;EAEF,MAAM,YAAY,MAAM,iBAAiB,eAAe,QAAQ;AAChE,MAAI,UACF,SAAQ,IAAI,4BAA4B,YAAY;AAItD,MAAI,~~CAAC,~~GAAG,WAAW,SAAS,~~EAAE~~;~~AAC5B~~,~~WAAQ~~,IAAI,4CAA4C;AACxD,~~SAAM~~,eAAe,GAAG,UAAU,0BAA0B,QAAQ;;~~AAGtE~~,qBAAmB;GAAE;GAAS;GAAW;GAAe,CAAC;AAGzD,UAAQ,IAAI,iCAAiC;AAC7C,QAAM,mBAAmB;AACzB,UAAQ,IAAI,oBAAoB;AAEhC,8BAA4B;GAAE;GAAW;GAAkB,CAAC;AAG5D,UAAQ,IAAI,uCAAuC;AAInD,OAAK,MAAM,eAAe,iBACxB,KAAI,GAAG,WAAW,YAAY,EAAE;AAC9B,OAAI,UACF,SAAQ,IAAI,+BAA+B,YAAY;AAEzD,SAAM,eAAe,mBAAmB,YAAY,wBAAwB,QAAQ;;~~EAIxF~~,MAAM,mBAAmB,QAAQ,IAAI;AAErC,MAAI,CAAC,oBAAoB,CAAC,GAAG,WAAW,iBAAiB,EAAE;GACzD,MAAM,aAAa,kBAAkB,QAAQ;AAC7C,kBAAe,MAAM,6CAA6C;AAClE,kBAAe,KACb,sBAAsB,GAAG,KAAK,WAAW,CAAC,qCAAqC,GAAG,KAAK,iCAAiC,GACzH;AACD,WAAQ,KAAK,EAAE;;UAEV,OAAO;EACd,MAAM,eAAe,iBAAiB,QAAQ,MAAM,UAAU,OAAO,MAAM;AAC3E,iBAAe,MAAM,wBAAwB,aAAa;AAC1D,UAAQ,KAAK,EAAE;;;AAInB,MAAa,UAAU,OAAO,EAAE,YAAY,OAAO,gBAAgB,aAA2C;CAC5G,MAAM,UAAU,QAAQ,KAAK;CAE7B,MAAM,QAAQ,aAAa,QAAQ;CACnC,MAAM,UAAU,eAAe,QAAQ;AACvC,KAAI,MAAM,MAAM,SAAS,KAAK,SAAS,MAAM,CAAC,IAAI,QAAQ,MAAM,SAAS,KAAK,SAAS,MAAM,CAAC,CAC5F,OAAM,cAAc;EAAE;EAAS;EAAW;EAAe,CAAC;AAG5D,SAAQ,KAAK,yCAAyC;AAEtD,SAAQ,KAAK,EAAE"}
1	+ {"version":3,"file":"install.mjs","names":[],"sources":["../src/install.ts"],"sourcesContent":["import fs from 'node:fs'\nimport path from 'node:path'\nimport pc from 'picocolors'\nimport { getStepFiles, getStreamFiles } from './generate-locked-data'\nimport { activatePythonVenv, getSitePackagesPath } from './utils/activate-python-env'\nimport { ensureUvInstalled } from './utils/ensure-uv'\nimport { executeCommand } from './utils/execute-command'\nimport { installLambdaPythonPackages } from './utils/install-lambda-python-packages'\nimport { internalLogger } from './utils/internal-logger'\nimport { getPythonCommand } from './utils/python-version-utils'\nimport { getInstallCommand } from './utils/validate-python-environment'\n\ninterface InstallConfig {\n isVerbose?: boolean\n pythonVersion?: string\n}\n\ntype PythonInstallConfig = InstallConfig & { baseDir: string }\n\nexport const pythonInstall = async ({\n baseDir,\n isVerbose = false,\n pythonVersion = '3.13',\n}: PythonInstallConfig): Promise<void> => {\n const venvPath = path.join(baseDir, 'python_modules')\n console.log('📦 Installing Python dependencies...', venvPath)\n\n const coreRequirementsPath = path.join(baseDir, 'node_modules', 'motia', 'dist', 'requirements-core.txt')\n const snapRequirementsPath = path.join(baseDir, 'node_modules', 'motia', 'dist', 'requirements-snap.txt')\n const localRequirements = path.join(baseDir, 'requirements.txt')\n\n const requirementsList = [coreRequirementsPath, snapRequirementsPath, localRequirements]\n\n try {\n // Get the appropriate Python command\n const pythonCmd = await getPythonCommand(pythonVersion, baseDir)\n if (isVerbose) {\n console.log(`🐍 Using Python command: ${pythonCmd}`)\n }\n\n // Check if virtual environment exists\n if (fs.existsSync(venvPath)) {\n fs.rmSync(venvPath, { recursive: true, force: true })\n }\n\n console.log('📦 Creating Python virtual environment...')\n await executeCommand(`${pythonCmd} -m venv python_modules`, baseDir)\n\n const sitePackagesPath = getSitePackagesPath({ baseDir, pythonVersion })\n\n if (!sitePackagesPath \|\| !fs.existsSync(sitePackagesPath)) {\n const installCmd = getInstallCommand(baseDir)\n internalLogger.error('Python virtual environment was not created')\n internalLogger.info(\n `Please try running ${pc.cyan(installCmd)} or manually create the venv with: ${pc.cyan('python3 -m venv python_modules')}`,\n )\n process.exit(1)\n }\n\n activatePythonVenv({ baseDir, isVerbose, pythonVersion })\n\n // Ensure UV is installed\n console.log('🔧 Checking UV installation...')\n await ensureUvInstalled()\n console.log('✅ UV is available')\n\n installLambdaPythonPackages({ isVerbose, requirementsList })\n\n // Install requirements\n console.log('📥 Installing Python dependencies...')\n\n // Core requirements\n\n for (const requirement of requirementsList) {\n if (fs.existsSync(requirement)) {\n if (isVerbose) {\n console.log('📄 Using requirements from:', requirement)\n }\n await executeCommand(`pip install -r \"${requirement}\" --only-binary=:all:`, baseDir)\n }\n }\n } catch (error) {\n const errorMessage = error instanceof Error ? error.message : String(error)\n internalLogger.error('Installation failed:', errorMessage)\n process.exit(1)\n }\n}\n\nexport const install = async ({ isVerbose = false, pythonVersion = '3.13' }: InstallConfig): Promise<void> => {\n const baseDir = process.cwd()\n\n const steps = getStepFiles(baseDir)\n const streams = getStreamFiles(baseDir)\n if (steps.some((file) => file.endsWith('.py')) \|\| streams.some((file) => file.endsWith('.py'))) {\n await pythonInstall({ baseDir, isVerbose, pythonVersion })\n }\n\n console.info('✅ Installation completed successfully!')\n\n process.exit(0)\n}\n"],"mappings":";;;;;;;;;;;;;AAmBA,MAAa,gBAAgB,OAAO,EAClC,SACA,YAAY,OACZ,gBAAgB,aACwB;CACxC,MAAM,WAAW,KAAK,KAAK,SAAS,iBAAiB;AACrD,SAAQ,IAAI,wCAAwC,SAAS;CAM7D,MAAM,mBAAmB;EAJI,KAAK,KAAK,SAAS,gBAAgB,SAAS,QAAQ,wBAAwB;EAC5E,KAAK,KAAK,SAAS,gBAAgB,SAAS,QAAQ,wBAAwB;EAC/E,KAAK,KAAK,SAAS,mBAAmB;EAEwB;AAExF,KAAI;EAEF,MAAM,YAAY,MAAM,iBAAiB,eAAe,QAAQ;AAChE,MAAI,UACF,SAAQ,IAAI,4BAA4B,YAAY;AAItD,MAAI,GAAG,WAAW,SAAS,CACzB,IAAG,OAAO,UAAU;GAAE,WAAW;GAAM,OAAO;GAAM,CAAC;AAGvD,UAAQ,IAAI,4CAA4C;AACxD,QAAM,eAAe,GAAG,UAAU,0BAA0B,QAAQ;EAEpE,MAAM,mBAAmB,oBAAoB;GAAE;GAAS;GAAe,CAAC;AAExE,MAAI,CAAC,oBAAoB,CAAC,GAAG,WAAW,iBAAiB,EAAE;GACzD,MAAM,aAAa,kBAAkB,QAAQ;AAC7C,kBAAe,MAAM,6CAA6C;AAClE,kBAAe,KACb,sBAAsB,GAAG,KAAK,WAAW,CAAC,qCAAqC,GAAG,KAAK,iCAAiC,GACzH;AACD,WAAQ,KAAK,EAAE;;AAGjB,qBAAmB;GAAE;GAAS;GAAW;GAAe,CAAC;AAGzD,UAAQ,IAAI,iCAAiC;AAC7C,QAAM,mBAAmB;AACzB,UAAQ,IAAI,oBAAoB;AAEhC,8BAA4B;GAAE;GAAW;GAAkB,CAAC;AAG5D,UAAQ,IAAI,uCAAuC;AAInD,OAAK,MAAM,eAAe,iBACxB,KAAI,GAAG,WAAW,YAAY,EAAE;AAC9B,OAAI,UACF,SAAQ,IAAI,+BAA+B,YAAY;AAEzD,SAAM,eAAe,mBAAmB,YAAY,wBAAwB,QAAQ;;UAGjF,OAAO;EACd,MAAM,eAAe,iBAAiB,QAAQ,MAAM,UAAU,OAAO,MAAM;AAC3E,iBAAe,MAAM,wBAAwB,aAAa;AAC1D,UAAQ,KAAK,EAAE;;;AAInB,MAAa,UAAU,OAAO,EAAE,YAAY,OAAO,gBAAgB,aAA2C;CAC5G,MAAM,UAAU,QAAQ,KAAK;CAE7B,MAAM,QAAQ,aAAa,QAAQ;CACnC,MAAM,UAAU,eAAe,QAAQ;AACvC,KAAI,MAAM,MAAM,SAAS,KAAK,SAAS,MAAM,CAAC,IAAI,QAAQ,MAAM,SAAS,KAAK,SAAS,MAAM,CAAC,CAC5F,OAAM,cAAc;EAAE;EAAS;EAAW;EAAe,CAAC;AAG5D,SAAQ,KAAK,yCAAyC;AAEtD,SAAQ,KAAK,EAAE"}

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "name": "motia",
   "description": "Build production-grade backends with a single primitive. APIs, background jobs, Queues, Workflows, and AI agents - unified in one system with built-in State management, Streaming, and Observability.",
-  "version": "0.17.11-beta.193",
+  "version": "0.17.12-beta.194",
   "license": "Elastic-2.0",
   "type": "module",
   "repository": {
@@ -46,13 +46,13 @@
     "table": "^6.9.0",
     "ts-node": "^10.9.2",
     "zod": "^4.1.13",
-    "@motiadev/adapter-bullmq-events": "0.17.11-beta.193",
-    "@motiadev/adapter-redis-streams": "0.17.11-beta.193",
-    "@motiadev/adapter-redis-cron": "0.17.11-beta.193",
-    "@motiadev/adapter-redis-state": "0.17.11-beta.193",
-    "@motiadev/core": "0.17.11-beta.193",
-    "@motiadev/stream-client-node": "0.17.11-beta.193",
-    "@motiadev/workbench": "0.17.11-beta.193"
+    "@motiadev/adapter-redis-cron": "0.17.12-beta.194",
+    "@motiadev/adapter-bullmq-events": "0.17.12-beta.194",
+    "@motiadev/adapter-redis-streams": "0.17.12-beta.194",
+    "@motiadev/adapter-redis-state": "0.17.12-beta.194",
+    "@motiadev/stream-client-node": "0.17.12-beta.194",
+    "@motiadev/workbench": "0.17.12-beta.194",
+    "@motiadev/core": "0.17.12-beta.194"
   },
   "devDependencies": {
     "@amplitude/analytics-types": "^2.9.2",