npm - motia - Versions diffs - 0.17.1-beta.183-767430 → 0.17.2-beta.184-886580 - Mend

motia 0.17.1-beta.183-767430 → 0.17.2-beta.184-886580

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 (5) hide show

package/dist/create/index.mjs +2 -1
package/dist/create/index.mjs.map +1 -1
package/dist/create/templates/nodejs/tutorial/tutorial.tsx.txt +217 -81
package/dist/create/templates/python/tutorial/tutorial.tsx.txt +217 -81
package/package.json +8 -8

package/dist/create/index.mjs CHANGED Viewed

@@ -31,7 +31,8 @@ const installRequiredDependencies = async (packageManager, rootDir, context) =>
 	const devDependencies = [
 		"ts-node@10.9.2",
 		"typescript@5.7.3",
-		"@types/react@19.1.1"
+		"@types/react@19.1.1",
+		`@motiadev/workbench@${version}`
 	].join(" ");
 	try {
 		await executeCommand(`${installCommand} ${dependencies}`, rootDir);

package/dist/create/index.mjs.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"index.mjs","names":["packageManager: string"],"sources":["../../src/create/index.ts"],"sourcesContent":["import fs from 'fs'\nimport path from 'path'\nimport pc from 'picocolors'\nimport { fileURLToPath } from 'url'\nimport type { CliContext, Message } from '../cloud/config-utils'\nimport { generateTypes } from '../generate-types'\nimport { pythonInstall } from '../install'\nimport { pluginDependencies } from '../plugins/plugin-dependencies'\nimport { executeCommand } from '../utils/execute-command'\nimport { getPackageManager, getPackageManagerFromEnv } from '../utils/get-package-manager'\nimport { version } from '../version'\nimport { pullRules } from './pull-rules'\nimport { setupTemplate } from './setup-template'\nimport { checkIfDirectoryExists, checkIfFileExists } from './utils'\n\nconst __dirname = path.dirname(fileURLToPath(import.meta.url))\n\nconst installRequiredDependencies = async (packageManager: string, rootDir: string, context: CliContext) => {\n context.log('installing-dependencies', (message: Message) => message.tag('info').append('Installing dependencies...'))\n\n const installCommand = {\n npm: 'npm install --save',\n yarn: 'yarn add',\n pnpm: 'pnpm add',\n bun: 'bun add',\n }[packageManager]\n\n const dependencies = [\n `motia@${version}`,\n 'zod@4.1.12',\n `@motiadev/adapter-bullmq-events@${version}`,\n ...pluginDependencies.map((dep: string) => `${dep}@${version}`),\n ].join(' ')\n\n const devDependencies = ['ts-node@10.9.2', 'typescript@5.7.3', '@types/react@19.1.1'].join(' ')\n\n try {\n await executeCommand(`${installCommand} ${dependencies}`, rootDir)\n await executeCommand(`${installCommand} -D ${devDependencies}`, rootDir)\n\n context.log('dependencies-installed', (message: Message) => message.tag('success').append('Dependencies installed'))\n } catch (error) {\n console.error('❌ Failed to install dependencies:', error)\n }\n}\n\nconst preparePackageManager = async (rootDir: string, context: CliContext, detectFromParent = false) => {\n const detectionDir = detectFromParent ? process.cwd() : rootDir\n const envPackageManager = getPackageManagerFromEnv()\n const packageManager = getPackageManager(detectionDir)\n\n const isFallback =\n !envPackageManager && packageManager === 'npm' && !checkIfFileExists(detectionDir, 'package-lock.json')\n\n if (isFallback) {\n context.log('package-manager-using-default', (message: Message) =>\n message.tag('info').append('Using default package manager').append(packageManager, 'gray'),\n )\n } else {\n context.log('package-manager-detected', (message: Message) =>\n message.tag('info').append('Detected package manager').append(packageManager, 'gray'),\n )\n }\n\n return packageManager\n}\n\nconst installNodeDependencies = async (rootDir: string, context: CliContext) => {\n const packageManager = await preparePackageManager(rootDir, context)\n\n await installRequiredDependencies(packageManager, rootDir, context).catch((error: unknown) => {\n context.log('failed-to-install-dependencies', (message: Message) =>\n message.tag('failed').append('Failed to install dependencies'),\n )\n console.error(error)\n })\n\n return packageManager\n}\n\ntype Args = {\n projectName: string\n template: string\n cursorEnabled: boolean\n context: CliContext\n skipTutorialTemplates?: boolean\n skipRedis?: boolean\n}\n\nexport const create = async ({\n projectName,\n template,\n cursorEnabled,\n context,\n skipRedis = false,\n}: Args): Promise<void> => {\n console.log(\n '\\n\\n' +\n `\n _____ ______ ______ ______\n /'\\\\_/\\`\\\\/\\\\ __\\`\\\\/\\\\__ _\\\\/\\\\__ _\\\\ /\\\\ _ \\\\\n /\\\\ \\\\ \\\\ \\\\/\\\\ \\\\/_/\\\\ \\\\/\\\\/_/\\\\ \\\\/ \\\\ \\\\ \\\\L\\\\ \\\\\n \\\\ \\\\ \\\\__\\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ __ \\\\\n \\\\ \\\\ \\\\_/\\\\ \\\\ \\\\ \\\\_\\\\ \\\\ \\\\ \\\\ \\\\ \\\\_\\\\ \\\\__\\\\ \\\\ \\\\/\\\\ \\\\\n \\\\ \\\\_\\\\\\\\ \\\\_\\\\ \\\\_____\\\\ \\\\ \\\\_\\\\ /\\\\_____\\\\\\\\ \\\\_\\\\ \\\\_\\\\\n \\\\/_/ \\\\/_/\\\\/_____/ \\\\/_/ \\\\/_____/ \\\\/_/\\\\/_/\n ` +\n '\\n\\n',\n )\n\n const isCurrentDir = projectName === '.' \|\| projectName === './' \|\| projectName === '.\\\\'\n const rootDir = isCurrentDir ? process.cwd() : path.join(process.cwd(), projectName)\n const isPluginTemplate = template === 'plugin'\n\n process.env.REDISMS_DISABLE_POSTINSTALL = '1'\n if (!isCurrentDir && !checkIfDirectoryExists(rootDir)) {\n fs.mkdirSync(path.join(rootDir))\n context.log('directory-created', (message: Message) =>\n message.tag('success').append('Directory created ').append(projectName, 'gray'),\n )\n } else {\n context.log('directory-using', (message: Message) => message.tag('info').append('Using current directory'))\n }\n\n // Plugin template handles package.json differently (via template)\n if (!isPluginTemplate && !checkIfFileExists(rootDir, 'package.json')) {\n const finalProjectName =\n !projectName \|\| projectName === '.' \|\| projectName === './' \|\| projectName === '.\\\\'\n ? path.basename(process.cwd())\n : projectName.trim()\n\n const packageJsonContent = {\n name: finalProjectName,\n description: '',\n type: 'module',\n scripts: {\n postinstall: 'motia install',\n dev: 'motia dev',\n start: 'motia start',\n 'generate-types': 'motia generate-types',\n build: 'motia build',\n clean: 'rm -rf dist node_modules python_modules .motia .mermaid',\n //'generate:config': 'motia get-config --output ./', TODO: doesnt work at the moment\n },\n keywords: ['motia'],\n }\n\n fs.writeFileSync(path.join(rootDir, 'package.json'), JSON.stringify(packageJsonContent, null, 2))\n\n context.log('package-json-created', (message: Message) =>\n message.tag('success').append('File').append('package.json', 'cyan').append('has been created.'),\n )\n } else if (!isPluginTemplate) {\n const packageJsonPath = path.join(rootDir, 'package.json')\n const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'))\n\n if (!packageJson.scripts) {\n packageJson.scripts = {}\n }\n\n if (!packageJson.scripts.dev) {\n packageJson.scripts.dev = 'motia dev'\n } else {\n packageJson.scripts.olddev = packageJson.scripts.dev\n packageJson.scripts.dev = 'motia dev'\n context.log('dev-command-already-exists', (message: Message) =>\n message.tag('warning').append('dev command already exists in package.json'),\n )\n }\n\n fs.writeFileSync(packageJsonPath, JSON.stringify(packageJson, null, 2))\n context.log('dev-command-updated', (message: Message) =>\n message\n .tag('success')\n .append('Updated')\n .append('dev', 'gray')\n .append('command to')\n .append('package.json', 'gray'),\n )\n }\n\n // Plugin template handles tsconfig.json via template\n if (!isPluginTemplate && !checkIfFileExists(rootDir, 'tsconfig.json')) {\n const tsconfigContent = {\n compilerOptions: {\n target: 'ES2020',\n module: 'ESNext',\n moduleResolution: 'bundler',\n allowImportingTsExtensions: true,\n noEmit: true,\n esModuleInterop: true,\n strict: true,\n skipLibCheck: true,\n forceConsistentCasingInFileNames: true,\n resolveJsonModule: true,\n allowJs: true,\n outDir: 'dist',\n rootDir: '.',\n baseUrl: '.',\n jsx: 'react-jsx',\n },\n include: ['*/.ts', 'motia.config.ts', '*/.tsx', 'types.d.ts', '*/.jsx'],\n exclude: ['node_modules', 'dist', 'tests'],\n }\n\n fs.writeFileSync(path.join(rootDir, 'tsconfig.json'), JSON.stringify(tsconfigContent, null, 2))\n context.log('tsconfig-json-created', (message: Message) =>\n message.tag('success').append('File').append('tsconfig.json', 'cyan').append('has been created.'),\n )\n }\n\n // Plugin template handles .gitignore via template\n if (!isPluginTemplate && !checkIfFileExists(rootDir, '.gitignore')) {\n const gitignoreContent = [\n 'node_modules',\n 'python_modules',\n '.venv',\n 'venv',\n '.motia',\n '.mermaid',\n 'dist',\n '*.pyc',\n ].join('\\n')\n\n fs.writeFileSync(path.join(rootDir, '.gitignore'), gitignoreContent)\n context.log('gitignore-created', (message: Message) =>\n message.tag('success').append('File').append('.gitignore', 'cyan').append('has been created.'),\n )\n }\n\n // Skip cursor rules for plugin template\n if (!isPluginTemplate && cursorEnabled) {\n await pullRules({ force: true, rootDir }, context)\n }\n\n if (template) {\n await setupTemplate(template, rootDir, context)\n }\n\n if (!isPluginTemplate && skipRedis) {\n const motiaConfigPath = path.join(rootDir, 'motia.config.ts')\n\n const templatePath = path.join(__dirname, 'templates/motia.config.external-redis.ts.txt')\n const templateContent = fs.readFileSync(templatePath, 'utf-8')\n fs.writeFileSync(motiaConfigPath, templateContent)\n context.log('motia-config-created', (message: Message) =>\n message.tag('success').append('File').append('motia.config.ts', 'cyan').append('has been created.'),\n )\n }\n\n let packageManager: string\n if (!isPluginTemplate) {\n packageManager = await installNodeDependencies(rootDir, context)\n\n if (template.includes('python') \|\| template.includes('multilang')) {\n await pythonInstall({ baseDir: rootDir })\n }\n\n await generateTypes(rootDir)\n } else {\n packageManager = await preparePackageManager(rootDir, context, true)\n\n context.log('installing-plugin-dependencies', (message: Message) =>\n message.tag('info').append('Installing plugin dependencies...'),\n )\n\n const installCommand = {\n npm: 'npm install',\n yarn: 'yarn',\n pnpm: 'pnpm install',\n bun: 'bun install',\n }[packageManager]\n\n try {\n await executeCommand(installCommand!, rootDir)\n context.log('plugin-dependencies-installed', (message: Message) =>\n message.tag('success').append('Plugin dependencies installed'),\n )\n } catch (error) {\n context.log('failed-to-install-plugin-dependencies', (message: Message) =>\n message.tag('failed').append('Failed to install plugin dependencies'),\n )\n console.error(error)\n }\n }\n\n const projectDirName = path.basename(rootDir)\n const devCommand = `${packageManager} run dev`\n const port = 3000\n const cdCommand = isCurrentDir ? '' : `${pc.cyan(`cd ${projectDirName}`)}\\n `\n\n context.log('success-blank', (message) => message.text(''))\n context.log('success-header', (message) =>\n message.text(`${pc.green('✨')} ${pc.bold('All set! Your project is ready to go.')}`),\n )\n context.log('success-blank-2', (message) => message.text(''))\n context.log('success-get-started', (message) => message.text('Get started:'))\n context.log('success-blank-3', (message) => message.text(''))\n context.log('success-commands', (message) => message.text(` ${cdCommand}${pc.cyan(devCommand)}`))\n context.log('success-blank-4', (message) => message.text(''))\n context.log('success-open', (message) => message.text(`Then open ${pc.cyan(`http://localhost:${port}`)}`))\n context.log('success-blank-5', (message: Message) => message.text(''))\n context.log('success-docs', (message) => message.text(`Docs: ${pc.cyan('https://www.motia.dev/docs')}`))\n context.log('success-blank-6', (message) => message.text(''))\n if (skipRedis) {\n context.log('redis-skip-warning', (message: Message) =>\n message\n .tag('warning')\n .append(\n '⚠️ You skipped Redis binary installation. Make sure to provide a Redis connection before running Motia.',\n ),\n )\n context.log('success-blank-7', (message) => message.text(''))\n }\n context.log('success-signoff', (message) => message.text('Happy coding! 🚀'))\n context.log('success-blank-8', (message) => message.text(''))\n}\n"],"mappings":";;;;;;;;;;;;;;;AAeA,MAAM,YAAY,KAAK,QAAQ,cAAc,OAAO,KAAK,IAAI,CAAC;AAE9D,MAAM,8BAA8B,OAAO,gBAAwB,SAAiB,YAAwB;AAC1G,SAAQ,IAAI,4BAA4B,YAAqB,QAAQ,IAAI,OAAO,CAAC,OAAO,6BAA6B,CAAC;CAEtH,MAAM,iBAAiB;EACrB,KAAK;EACL,MAAM;EACN,MAAM;EACN,KAAK;EACN,CAAC;CAEF,MAAM,eAAe;EACnB,SAAS;EACT;EACA,mCAAmC;EACnC,GAAG,mBAAmB,KAAK,QAAgB,GAAG,IAAI,GAAG,UAAU;EAChE,CAAC,KAAK,IAAI;CAEX,MAAM,kBAAkB;EAAC;EAAkB;EAAoB;EAAsB,CAAC,KAAK,IAAI;AAE/F,KAAI;AACF,QAAM,eAAe,GAAG,eAAe,GAAG,gBAAgB,QAAQ;AAClE,QAAM,eAAe,GAAG,eAAe,MAAM,mBAAmB,QAAQ;AAExE,UAAQ,IAAI,2BAA2B,YAAqB,QAAQ,IAAI,UAAU,CAAC,OAAO,yBAAyB,CAAC;UAC7G,OAAO;AACd,UAAQ,MAAM,qCAAqC,MAAM;;;AAI7D,MAAM,wBAAwB,OAAO,SAAiB,SAAqB,mBAAmB,UAAU;CACtG,MAAM,eAAe,mBAAmB,QAAQ,KAAK,GAAG;CACxD,MAAM,oBAAoB,0BAA0B;CACpD,MAAM,iBAAiB,kBAAkB,aAAa;AAKtD,KAFE,CAAC,qBAAqB,mBAAmB,SAAS,CAAC,kBAAkB,cAAc,oBAAoB,CAGvG,SAAQ,IAAI,kCAAkC,YAC5C,QAAQ,IAAI,OAAO,CAAC,OAAO,gCAAgC,CAAC,OAAO,gBAAgB,OAAO,CAC3F;KAED,SAAQ,IAAI,6BAA6B,YACvC,QAAQ,IAAI,OAAO,CAAC,OAAO,2BAA2B,CAAC,OAAO,gBAAgB,OAAO,CACtF;AAGH,QAAO;;AAGT,MAAM,0BAA0B,OAAO,SAAiB,YAAwB;CAC9E,MAAM,iBAAiB,MAAM,sBAAsB,SAAS,QAAQ;AAEpE,OAAM,4BAA4B,gBAAgB,SAAS,QAAQ,CAAC,OAAO,UAAmB;AAC5F,UAAQ,IAAI,mCAAmC,YAC7C,QAAQ,IAAI,SAAS,CAAC,OAAO,iCAAiC,CAC/D;AACD,UAAQ,MAAM,MAAM;GACpB;AAEF,QAAO;;AAYT,MAAa,SAAS,OAAO,EAC3B,aACA,UACA,eACA,SACA,YAAY,YACa;AACzB,SAAQ,IACN,sbAWD;CAED,MAAM,eAAe,gBAAgB,OAAO,gBAAgB,QAAQ,gBAAgB;CACpF,MAAM,UAAU,eAAe,QAAQ,KAAK,GAAG,KAAK,KAAK,QAAQ,KAAK,EAAE,YAAY;CACpF,MAAM,mBAAmB,aAAa;AAEtC,SAAQ,IAAI,8BAA8B;AAC1C,KAAI,CAAC,gBAAgB,CAAC,uBAAuB,QAAQ,EAAE;AACrD,KAAG,UAAU,KAAK,KAAK,QAAQ,CAAC;AAChC,UAAQ,IAAI,sBAAsB,YAChC,QAAQ,IAAI,UAAU,CAAC,OAAO,qBAAqB,CAAC,OAAO,aAAa,OAAO,CAChF;OAED,SAAQ,IAAI,oBAAoB,YAAqB,QAAQ,IAAI,OAAO,CAAC,OAAO,0BAA0B,CAAC;AAI7G,KAAI,CAAC,oBAAoB,CAAC,kBAAkB,SAAS,eAAe,EAAE;EAMpE,MAAM,qBAAqB;GACzB,MALA,CAAC,eAAe,gBAAgB,OAAO,gBAAgB,QAAQ,gBAAgB,QAC3E,KAAK,SAAS,QAAQ,KAAK,CAAC,GAC5B,YAAY,MAAM;GAItB,aAAa;GACb,MAAM;GACN,SAAS;IACP,aAAa;IACb,KAAK;IACL,OAAO;IACP,kBAAkB;IAClB,OAAO;IACP,OAAO;IAER;GACD,UAAU,CAAC,QAAQ;GACpB;AAED,KAAG,cAAc,KAAK,KAAK,SAAS,eAAe,EAAE,KAAK,UAAU,oBAAoB,MAAM,EAAE,CAAC;AAEjG,UAAQ,IAAI,yBAAyB,YACnC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,gBAAgB,OAAO,CAAC,OAAO,oBAAoB,CACjG;YACQ,CAAC,kBAAkB;EAC5B,MAAM,kBAAkB,KAAK,KAAK,SAAS,eAAe;EAC1D,MAAM,cAAc,KAAK,MAAM,GAAG,aAAa,iBAAiB,QAAQ,CAAC;AAEzE,MAAI,CAAC,YAAY,QACf,aAAY,UAAU,EAAE;AAG1B,MAAI,CAAC,YAAY,QAAQ,IACvB,aAAY,QAAQ,MAAM;OACrB;AACL,eAAY,QAAQ,SAAS,YAAY,QAAQ;AACjD,eAAY,QAAQ,MAAM;AAC1B,WAAQ,IAAI,+BAA+B,YACzC,QAAQ,IAAI,UAAU,CAAC,OAAO,6CAA6C,CAC5E;;AAGH,KAAG,cAAc,iBAAiB,KAAK,UAAU,aAAa,MAAM,EAAE,CAAC;AACvE,UAAQ,IAAI,wBAAwB,YAClC,QACG,IAAI,UAAU,CACd,OAAO,UAAU,CACjB,OAAO,OAAO,OAAO,CACrB,OAAO,aAAa,CACpB,OAAO,gBAAgB,OAAO,CAClC;;AAIH,KAAI,CAAC,oBAAoB,CAAC,kBAAkB,SAAS,gBAAgB,EAAE;AAuBrE,KAAG,cAAc,KAAK,KAAK,SAAS,gBAAgB,EAAE,KAAK,UAtBnC;GACtB,iBAAiB;IACf,QAAQ;IACR,QAAQ;IACR,kBAAkB;IAClB,4BAA4B;IAC5B,QAAQ;IACR,iBAAiB;IACjB,QAAQ;IACR,cAAc;IACd,kCAAkC;IAClC,mBAAmB;IACnB,SAAS;IACT,QAAQ;IACR,SAAS;IACT,SAAS;IACT,KAAK;IACN;GACD,SAAS;IAAC;IAAW;IAAmB;IAAY;IAAc;IAAW;GAC7E,SAAS;IAAC;IAAgB;IAAQ;IAAQ;GAC3C,EAEqF,MAAM,EAAE,CAAC;AAC/F,UAAQ,IAAI,0BAA0B,YACpC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,iBAAiB,OAAO,CAAC,OAAO,oBAAoB,CAClG;;AAIH,KAAI,CAAC,oBAAoB,CAAC,kBAAkB,SAAS,aAAa,EAAE;EAClE,MAAM,mBAAmB;GACvB;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACD,CAAC,KAAK,KAAK;AAEZ,KAAG,cAAc,KAAK,KAAK,SAAS,aAAa,EAAE,iBAAiB;AACpE,UAAQ,IAAI,sBAAsB,YAChC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,cAAc,OAAO,CAAC,OAAO,oBAAoB,CAC/F;;AAIH,KAAI,CAAC,oBAAoB,cACvB,OAAM,UAAU;EAAE,OAAO;EAAM;EAAS,EAAE,QAAQ;AAGpD,KAAI,SACF,OAAM,cAAc,UAAU,SAAS,QAAQ;AAGjD,KAAI,CAAC,oBAAoB,WAAW;EAClC,MAAM,kBAAkB,KAAK,KAAK,SAAS,kBAAkB;EAE7D,MAAM,eAAe,KAAK,KAAK,WAAW,+CAA+C;EACzF,MAAM,kBAAkB,GAAG,aAAa,cAAc,QAAQ;AAC9D,KAAG,cAAc,iBAAiB,gBAAgB;AAClD,UAAQ,IAAI,yBAAyB,YACnC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,mBAAmB,OAAO,CAAC,OAAO,oBAAoB,CACpG;;CAGH,IAAIA;AACJ,KAAI,CAAC,kBAAkB;AACrB,mBAAiB,MAAM,wBAAwB,SAAS,QAAQ;AAEhE,MAAI,SAAS,SAAS,SAAS,IAAI,SAAS,SAAS,YAAY,CAC/D,OAAM,cAAc,EAAE,SAAS,SAAS,CAAC;AAG3C,QAAM,cAAc,QAAQ;QACvB;AACL,mBAAiB,MAAM,sBAAsB,SAAS,SAAS,KAAK;AAEpE,UAAQ,IAAI,mCAAmC,YAC7C,QAAQ,IAAI,OAAO,CAAC,OAAO,oCAAoC,CAChE;EAED,MAAM,iBAAiB;GACrB,KAAK;GACL,MAAM;GACN,MAAM;GACN,KAAK;GACN,CAAC;AAEF,MAAI;AACF,SAAM,eAAe,gBAAiB,QAAQ;AAC9C,WAAQ,IAAI,kCAAkC,YAC5C,QAAQ,IAAI,UAAU,CAAC,OAAO,gCAAgC,CAC/D;WACM,OAAO;AACd,WAAQ,IAAI,0CAA0C,YACpD,QAAQ,IAAI,SAAS,CAAC,OAAO,wCAAwC,CACtE;AACD,WAAQ,MAAM,MAAM;;;CAIxB,MAAM,iBAAiB,KAAK,SAAS,QAAQ;CAC7C,MAAM,aAAa,GAAG,eAAe;CACrC,MAAM,OAAO;CACb,MAAM,YAAY,eAAe,KAAK,GAAG,GAAG,KAAK,MAAM,iBAAiB,CAAC;AAEzE,SAAQ,IAAI,kBAAkB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC3D,SAAQ,IAAI,mBAAmB,YAC7B,QAAQ,KAAK,GAAG,GAAG,MAAM,IAAI,CAAC,GAAG,GAAG,KAAK,wCAAwC,GAAG,CACrF;AACD,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,SAAQ,IAAI,wBAAwB,YAAY,QAAQ,KAAK,eAAe,CAAC;AAC7E,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,SAAQ,IAAI,qBAAqB,YAAY,QAAQ,KAAK,KAAK,YAAY,GAAG,KAAK,WAAW,GAAG,CAAC;AAClG,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,SAAQ,IAAI,iBAAiB,YAAY,QAAQ,KAAK,aAAa,GAAG,KAAK,oBAAoB,OAAO,GAAG,CAAC;AAC1G,SAAQ,IAAI,oBAAoB,YAAqB,QAAQ,KAAK,GAAG,CAAC;AACtE,SAAQ,IAAI,iBAAiB,YAAY,QAAQ,KAAK,SAAS,GAAG,KAAK,6BAA6B,GAAG,CAAC;AACxG,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,KAAI,WAAW;AACb,UAAQ,IAAI,uBAAuB,YACjC,QACG,IAAI,UAAU,CACd,OACC,2GACD,CACJ;AACD,UAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;;AAE/D,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,mBAAmB,CAAC;AAC7E,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC"}
1	+ {"version":3,"file":"index.mjs","names":["packageManager: string"],"sources":["../../src/create/index.ts"],"sourcesContent":["import fs from 'fs'\nimport path from 'path'\nimport pc from 'picocolors'\nimport { fileURLToPath } from 'url'\nimport type { CliContext, Message } from '../cloud/config-utils'\nimport { generateTypes } from '../generate-types'\nimport { pythonInstall } from '../install'\nimport { pluginDependencies } from '../plugins/plugin-dependencies'\nimport { executeCommand } from '../utils/execute-command'\nimport { getPackageManager, getPackageManagerFromEnv } from '../utils/get-package-manager'\nimport { version } from '../version'\nimport { pullRules } from './pull-rules'\nimport { setupTemplate } from './setup-template'\nimport { checkIfDirectoryExists, checkIfFileExists } from './utils'\n\nconst __dirname = path.dirname(fileURLToPath(import.meta.url))\n\nconst installRequiredDependencies = async (packageManager: string, rootDir: string, context: CliContext) => {\n context.log('installing-dependencies', (message: Message) => message.tag('info').append('Installing dependencies...'))\n\n const installCommand = {\n npm: 'npm install --save',\n yarn: 'yarn add',\n pnpm: 'pnpm add',\n bun: 'bun add',\n }[packageManager]\n\n const dependencies = [\n `motia@${version}`,\n 'zod@4.1.12',\n `@motiadev/adapter-bullmq-events@${version}`,\n ...pluginDependencies.map((dep: string) => `${dep}@${version}`),\n ].join(' ')\n\n const devDependencies = [\n 'ts-node@10.9.2',\n 'typescript@5.7.3',\n '@types/react@19.1.1',\n `@motiadev/workbench@${version}`,\n ].join(' ')\n\n try {\n await executeCommand(`${installCommand} ${dependencies}`, rootDir)\n await executeCommand(`${installCommand} -D ${devDependencies}`, rootDir)\n\n context.log('dependencies-installed', (message: Message) => message.tag('success').append('Dependencies installed'))\n } catch (error) {\n console.error('❌ Failed to install dependencies:', error)\n }\n}\n\nconst preparePackageManager = async (rootDir: string, context: CliContext, detectFromParent = false) => {\n const detectionDir = detectFromParent ? process.cwd() : rootDir\n const envPackageManager = getPackageManagerFromEnv()\n const packageManager = getPackageManager(detectionDir)\n\n const isFallback =\n !envPackageManager && packageManager === 'npm' && !checkIfFileExists(detectionDir, 'package-lock.json')\n\n if (isFallback) {\n context.log('package-manager-using-default', (message: Message) =>\n message.tag('info').append('Using default package manager').append(packageManager, 'gray'),\n )\n } else {\n context.log('package-manager-detected', (message: Message) =>\n message.tag('info').append('Detected package manager').append(packageManager, 'gray'),\n )\n }\n\n return packageManager\n}\n\nconst installNodeDependencies = async (rootDir: string, context: CliContext) => {\n const packageManager = await preparePackageManager(rootDir, context)\n\n await installRequiredDependencies(packageManager, rootDir, context).catch((error: unknown) => {\n context.log('failed-to-install-dependencies', (message: Message) =>\n message.tag('failed').append('Failed to install dependencies'),\n )\n console.error(error)\n })\n\n return packageManager\n}\n\ntype Args = {\n projectName: string\n template: string\n cursorEnabled: boolean\n context: CliContext\n skipTutorialTemplates?: boolean\n skipRedis?: boolean\n}\n\nexport const create = async ({\n projectName,\n template,\n cursorEnabled,\n context,\n skipRedis = false,\n}: Args): Promise<void> => {\n console.log(\n '\\n\\n' +\n `\n _____ ______ ______ ______\n /'\\\\_/\\`\\\\/\\\\ __\\`\\\\/\\\\__ _\\\\/\\\\__ _\\\\ /\\\\ _ \\\\\n /\\\\ \\\\ \\\\ \\\\/\\\\ \\\\/_/\\\\ \\\\/\\\\/_/\\\\ \\\\/ \\\\ \\\\ \\\\L\\\\ \\\\\n \\\\ \\\\ \\\\__\\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ \\\\ __ \\\\\n \\\\ \\\\ \\\\_/\\\\ \\\\ \\\\ \\\\_\\\\ \\\\ \\\\ \\\\ \\\\ \\\\_\\\\ \\\\__\\\\ \\\\ \\\\/\\\\ \\\\\n \\\\ \\\\_\\\\\\\\ \\\\_\\\\ \\\\_____\\\\ \\\\ \\\\_\\\\ /\\\\_____\\\\\\\\ \\\\_\\\\ \\\\_\\\\\n \\\\/_/ \\\\/_/\\\\/_____/ \\\\/_/ \\\\/_____/ \\\\/_/\\\\/_/\n ` +\n '\\n\\n',\n )\n\n const isCurrentDir = projectName === '.' \|\| projectName === './' \|\| projectName === '.\\\\'\n const rootDir = isCurrentDir ? process.cwd() : path.join(process.cwd(), projectName)\n const isPluginTemplate = template === 'plugin'\n\n process.env.REDISMS_DISABLE_POSTINSTALL = '1'\n if (!isCurrentDir && !checkIfDirectoryExists(rootDir)) {\n fs.mkdirSync(path.join(rootDir))\n context.log('directory-created', (message: Message) =>\n message.tag('success').append('Directory created ').append(projectName, 'gray'),\n )\n } else {\n context.log('directory-using', (message: Message) => message.tag('info').append('Using current directory'))\n }\n\n // Plugin template handles package.json differently (via template)\n if (!isPluginTemplate && !checkIfFileExists(rootDir, 'package.json')) {\n const finalProjectName =\n !projectName \|\| projectName === '.' \|\| projectName === './' \|\| projectName === '.\\\\'\n ? path.basename(process.cwd())\n : projectName.trim()\n\n const packageJsonContent = {\n name: finalProjectName,\n description: '',\n type: 'module',\n scripts: {\n postinstall: 'motia install',\n dev: 'motia dev',\n start: 'motia start',\n 'generate-types': 'motia generate-types',\n build: 'motia build',\n clean: 'rm -rf dist node_modules python_modules .motia .mermaid',\n //'generate:config': 'motia get-config --output ./', TODO: doesnt work at the moment\n },\n keywords: ['motia'],\n }\n\n fs.writeFileSync(path.join(rootDir, 'package.json'), JSON.stringify(packageJsonContent, null, 2))\n\n context.log('package-json-created', (message: Message) =>\n message.tag('success').append('File').append('package.json', 'cyan').append('has been created.'),\n )\n } else if (!isPluginTemplate) {\n const packageJsonPath = path.join(rootDir, 'package.json')\n const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'))\n\n if (!packageJson.scripts) {\n packageJson.scripts = {}\n }\n\n if (!packageJson.scripts.dev) {\n packageJson.scripts.dev = 'motia dev'\n } else {\n packageJson.scripts.olddev = packageJson.scripts.dev\n packageJson.scripts.dev = 'motia dev'\n context.log('dev-command-already-exists', (message: Message) =>\n message.tag('warning').append('dev command already exists in package.json'),\n )\n }\n\n fs.writeFileSync(packageJsonPath, JSON.stringify(packageJson, null, 2))\n context.log('dev-command-updated', (message: Message) =>\n message\n .tag('success')\n .append('Updated')\n .append('dev', 'gray')\n .append('command to')\n .append('package.json', 'gray'),\n )\n }\n\n // Plugin template handles tsconfig.json via template\n if (!isPluginTemplate && !checkIfFileExists(rootDir, 'tsconfig.json')) {\n const tsconfigContent = {\n compilerOptions: {\n target: 'ES2020',\n module: 'ESNext',\n moduleResolution: 'bundler',\n allowImportingTsExtensions: true,\n noEmit: true,\n esModuleInterop: true,\n strict: true,\n skipLibCheck: true,\n forceConsistentCasingInFileNames: true,\n resolveJsonModule: true,\n allowJs: true,\n outDir: 'dist',\n rootDir: '.',\n baseUrl: '.',\n jsx: 'react-jsx',\n },\n include: ['*/.ts', 'motia.config.ts', '*/.tsx', 'types.d.ts', '*/.jsx'],\n exclude: ['node_modules', 'dist', 'tests'],\n }\n\n fs.writeFileSync(path.join(rootDir, 'tsconfig.json'), JSON.stringify(tsconfigContent, null, 2))\n context.log('tsconfig-json-created', (message: Message) =>\n message.tag('success').append('File').append('tsconfig.json', 'cyan').append('has been created.'),\n )\n }\n\n // Plugin template handles .gitignore via template\n if (!isPluginTemplate && !checkIfFileExists(rootDir, '.gitignore')) {\n const gitignoreContent = [\n 'node_modules',\n 'python_modules',\n '.venv',\n 'venv',\n '.motia',\n '.mermaid',\n 'dist',\n '*.pyc',\n ].join('\\n')\n\n fs.writeFileSync(path.join(rootDir, '.gitignore'), gitignoreContent)\n context.log('gitignore-created', (message: Message) =>\n message.tag('success').append('File').append('.gitignore', 'cyan').append('has been created.'),\n )\n }\n\n // Skip cursor rules for plugin template\n if (!isPluginTemplate && cursorEnabled) {\n await pullRules({ force: true, rootDir }, context)\n }\n\n if (template) {\n await setupTemplate(template, rootDir, context)\n }\n\n if (!isPluginTemplate && skipRedis) {\n const motiaConfigPath = path.join(rootDir, 'motia.config.ts')\n\n const templatePath = path.join(__dirname, 'templates/motia.config.external-redis.ts.txt')\n const templateContent = fs.readFileSync(templatePath, 'utf-8')\n fs.writeFileSync(motiaConfigPath, templateContent)\n context.log('motia-config-created', (message: Message) =>\n message.tag('success').append('File').append('motia.config.ts', 'cyan').append('has been created.'),\n )\n }\n\n let packageManager: string\n if (!isPluginTemplate) {\n packageManager = await installNodeDependencies(rootDir, context)\n\n if (template.includes('python') \|\| template.includes('multilang')) {\n await pythonInstall({ baseDir: rootDir })\n }\n\n await generateTypes(rootDir)\n } else {\n packageManager = await preparePackageManager(rootDir, context, true)\n\n context.log('installing-plugin-dependencies', (message: Message) =>\n message.tag('info').append('Installing plugin dependencies...'),\n )\n\n const installCommand = {\n npm: 'npm install',\n yarn: 'yarn',\n pnpm: 'pnpm install',\n bun: 'bun install',\n }[packageManager]\n\n try {\n await executeCommand(installCommand!, rootDir)\n context.log('plugin-dependencies-installed', (message: Message) =>\n message.tag('success').append('Plugin dependencies installed'),\n )\n } catch (error) {\n context.log('failed-to-install-plugin-dependencies', (message: Message) =>\n message.tag('failed').append('Failed to install plugin dependencies'),\n )\n console.error(error)\n }\n }\n\n const projectDirName = path.basename(rootDir)\n const devCommand = `${packageManager} run dev`\n const port = 3000\n const cdCommand = isCurrentDir ? '' : `${pc.cyan(`cd ${projectDirName}`)}\\n `\n\n context.log('success-blank', (message) => message.text(''))\n context.log('success-header', (message) =>\n message.text(`${pc.green('✨')} ${pc.bold('All set! Your project is ready to go.')}`),\n )\n context.log('success-blank-2', (message) => message.text(''))\n context.log('success-get-started', (message) => message.text('Get started:'))\n context.log('success-blank-3', (message) => message.text(''))\n context.log('success-commands', (message) => message.text(` ${cdCommand}${pc.cyan(devCommand)}`))\n context.log('success-blank-4', (message) => message.text(''))\n context.log('success-open', (message) => message.text(`Then open ${pc.cyan(`http://localhost:${port}`)}`))\n context.log('success-blank-5', (message: Message) => message.text(''))\n context.log('success-docs', (message) => message.text(`Docs: ${pc.cyan('https://www.motia.dev/docs')}`))\n context.log('success-blank-6', (message) => message.text(''))\n if (skipRedis) {\n context.log('redis-skip-warning', (message: Message) =>\n message\n .tag('warning')\n .append(\n '⚠️ You skipped Redis binary installation. Make sure to provide a Redis connection before running Motia.',\n ),\n )\n context.log('success-blank-7', (message) => message.text(''))\n }\n context.log('success-signoff', (message) => message.text('Happy coding! 🚀'))\n context.log('success-blank-8', (message) => message.text(''))\n}\n"],"mappings":";;;;;;;;;;;;;;;AAeA,MAAM,YAAY,KAAK,QAAQ,cAAc,OAAO,KAAK,IAAI,CAAC;AAE9D,MAAM,8BAA8B,OAAO,gBAAwB,SAAiB,YAAwB;AAC1G,SAAQ,IAAI,4BAA4B,YAAqB,QAAQ,IAAI,OAAO,CAAC,OAAO,6BAA6B,CAAC;CAEtH,MAAM,iBAAiB;EACrB,KAAK;EACL,MAAM;EACN,MAAM;EACN,KAAK;EACN,CAAC;CAEF,MAAM,eAAe;EACnB,SAAS;EACT;EACA,mCAAmC;EACnC,GAAG,mBAAmB,KAAK,QAAgB,GAAG,IAAI,GAAG,UAAU;EAChE,CAAC,KAAK,IAAI;CAEX,MAAM,kBAAkB;EACtB;EACA;EACA;EACA,uBAAuB;EACxB,CAAC,KAAK,IAAI;AAEX,KAAI;AACF,QAAM,eAAe,GAAG,eAAe,GAAG,gBAAgB,QAAQ;AAClE,QAAM,eAAe,GAAG,eAAe,MAAM,mBAAmB,QAAQ;AAExE,UAAQ,IAAI,2BAA2B,YAAqB,QAAQ,IAAI,UAAU,CAAC,OAAO,yBAAyB,CAAC;UAC7G,OAAO;AACd,UAAQ,MAAM,qCAAqC,MAAM;;;AAI7D,MAAM,wBAAwB,OAAO,SAAiB,SAAqB,mBAAmB,UAAU;CACtG,MAAM,eAAe,mBAAmB,QAAQ,KAAK,GAAG;CACxD,MAAM,oBAAoB,0BAA0B;CACpD,MAAM,iBAAiB,kBAAkB,aAAa;AAKtD,KAFE,CAAC,qBAAqB,mBAAmB,SAAS,CAAC,kBAAkB,cAAc,oBAAoB,CAGvG,SAAQ,IAAI,kCAAkC,YAC5C,QAAQ,IAAI,OAAO,CAAC,OAAO,gCAAgC,CAAC,OAAO,gBAAgB,OAAO,CAC3F;KAED,SAAQ,IAAI,6BAA6B,YACvC,QAAQ,IAAI,OAAO,CAAC,OAAO,2BAA2B,CAAC,OAAO,gBAAgB,OAAO,CACtF;AAGH,QAAO;;AAGT,MAAM,0BAA0B,OAAO,SAAiB,YAAwB;CAC9E,MAAM,iBAAiB,MAAM,sBAAsB,SAAS,QAAQ;AAEpE,OAAM,4BAA4B,gBAAgB,SAAS,QAAQ,CAAC,OAAO,UAAmB;AAC5F,UAAQ,IAAI,mCAAmC,YAC7C,QAAQ,IAAI,SAAS,CAAC,OAAO,iCAAiC,CAC/D;AACD,UAAQ,MAAM,MAAM;GACpB;AAEF,QAAO;;AAYT,MAAa,SAAS,OAAO,EAC3B,aACA,UACA,eACA,SACA,YAAY,YACa;AACzB,SAAQ,IACN,sbAWD;CAED,MAAM,eAAe,gBAAgB,OAAO,gBAAgB,QAAQ,gBAAgB;CACpF,MAAM,UAAU,eAAe,QAAQ,KAAK,GAAG,KAAK,KAAK,QAAQ,KAAK,EAAE,YAAY;CACpF,MAAM,mBAAmB,aAAa;AAEtC,SAAQ,IAAI,8BAA8B;AAC1C,KAAI,CAAC,gBAAgB,CAAC,uBAAuB,QAAQ,EAAE;AACrD,KAAG,UAAU,KAAK,KAAK,QAAQ,CAAC;AAChC,UAAQ,IAAI,sBAAsB,YAChC,QAAQ,IAAI,UAAU,CAAC,OAAO,qBAAqB,CAAC,OAAO,aAAa,OAAO,CAChF;OAED,SAAQ,IAAI,oBAAoB,YAAqB,QAAQ,IAAI,OAAO,CAAC,OAAO,0BAA0B,CAAC;AAI7G,KAAI,CAAC,oBAAoB,CAAC,kBAAkB,SAAS,eAAe,EAAE;EAMpE,MAAM,qBAAqB;GACzB,MALA,CAAC,eAAe,gBAAgB,OAAO,gBAAgB,QAAQ,gBAAgB,QAC3E,KAAK,SAAS,QAAQ,KAAK,CAAC,GAC5B,YAAY,MAAM;GAItB,aAAa;GACb,MAAM;GACN,SAAS;IACP,aAAa;IACb,KAAK;IACL,OAAO;IACP,kBAAkB;IAClB,OAAO;IACP,OAAO;IAER;GACD,UAAU,CAAC,QAAQ;GACpB;AAED,KAAG,cAAc,KAAK,KAAK,SAAS,eAAe,EAAE,KAAK,UAAU,oBAAoB,MAAM,EAAE,CAAC;AAEjG,UAAQ,IAAI,yBAAyB,YACnC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,gBAAgB,OAAO,CAAC,OAAO,oBAAoB,CACjG;YACQ,CAAC,kBAAkB;EAC5B,MAAM,kBAAkB,KAAK,KAAK,SAAS,eAAe;EAC1D,MAAM,cAAc,KAAK,MAAM,GAAG,aAAa,iBAAiB,QAAQ,CAAC;AAEzE,MAAI,CAAC,YAAY,QACf,aAAY,UAAU,EAAE;AAG1B,MAAI,CAAC,YAAY,QAAQ,IACvB,aAAY,QAAQ,MAAM;OACrB;AACL,eAAY,QAAQ,SAAS,YAAY,QAAQ;AACjD,eAAY,QAAQ,MAAM;AAC1B,WAAQ,IAAI,+BAA+B,YACzC,QAAQ,IAAI,UAAU,CAAC,OAAO,6CAA6C,CAC5E;;AAGH,KAAG,cAAc,iBAAiB,KAAK,UAAU,aAAa,MAAM,EAAE,CAAC;AACvE,UAAQ,IAAI,wBAAwB,YAClC,QACG,IAAI,UAAU,CACd,OAAO,UAAU,CACjB,OAAO,OAAO,OAAO,CACrB,OAAO,aAAa,CACpB,OAAO,gBAAgB,OAAO,CAClC;;AAIH,KAAI,CAAC,oBAAoB,CAAC,kBAAkB,SAAS,gBAAgB,EAAE;AAuBrE,KAAG,cAAc,KAAK,KAAK,SAAS,gBAAgB,EAAE,KAAK,UAtBnC;GACtB,iBAAiB;IACf,QAAQ;IACR,QAAQ;IACR,kBAAkB;IAClB,4BAA4B;IAC5B,QAAQ;IACR,iBAAiB;IACjB,QAAQ;IACR,cAAc;IACd,kCAAkC;IAClC,mBAAmB;IACnB,SAAS;IACT,QAAQ;IACR,SAAS;IACT,SAAS;IACT,KAAK;IACN;GACD,SAAS;IAAC;IAAW;IAAmB;IAAY;IAAc;IAAW;GAC7E,SAAS;IAAC;IAAgB;IAAQ;IAAQ;GAC3C,EAEqF,MAAM,EAAE,CAAC;AAC/F,UAAQ,IAAI,0BAA0B,YACpC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,iBAAiB,OAAO,CAAC,OAAO,oBAAoB,CAClG;;AAIH,KAAI,CAAC,oBAAoB,CAAC,kBAAkB,SAAS,aAAa,EAAE;EAClE,MAAM,mBAAmB;GACvB;GACA;GACA;GACA;GACA;GACA;GACA;GACA;GACD,CAAC,KAAK,KAAK;AAEZ,KAAG,cAAc,KAAK,KAAK,SAAS,aAAa,EAAE,iBAAiB;AACpE,UAAQ,IAAI,sBAAsB,YAChC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,cAAc,OAAO,CAAC,OAAO,oBAAoB,CAC/F;;AAIH,KAAI,CAAC,oBAAoB,cACvB,OAAM,UAAU;EAAE,OAAO;EAAM;EAAS,EAAE,QAAQ;AAGpD,KAAI,SACF,OAAM,cAAc,UAAU,SAAS,QAAQ;AAGjD,KAAI,CAAC,oBAAoB,WAAW;EAClC,MAAM,kBAAkB,KAAK,KAAK,SAAS,kBAAkB;EAE7D,MAAM,eAAe,KAAK,KAAK,WAAW,+CAA+C;EACzF,MAAM,kBAAkB,GAAG,aAAa,cAAc,QAAQ;AAC9D,KAAG,cAAc,iBAAiB,gBAAgB;AAClD,UAAQ,IAAI,yBAAyB,YACnC,QAAQ,IAAI,UAAU,CAAC,OAAO,OAAO,CAAC,OAAO,mBAAmB,OAAO,CAAC,OAAO,oBAAoB,CACpG;;CAGH,IAAIA;AACJ,KAAI,CAAC,kBAAkB;AACrB,mBAAiB,MAAM,wBAAwB,SAAS,QAAQ;AAEhE,MAAI,SAAS,SAAS,SAAS,IAAI,SAAS,SAAS,YAAY,CAC/D,OAAM,cAAc,EAAE,SAAS,SAAS,CAAC;AAG3C,QAAM,cAAc,QAAQ;QACvB;AACL,mBAAiB,MAAM,sBAAsB,SAAS,SAAS,KAAK;AAEpE,UAAQ,IAAI,mCAAmC,YAC7C,QAAQ,IAAI,OAAO,CAAC,OAAO,oCAAoC,CAChE;EAED,MAAM,iBAAiB;GACrB,KAAK;GACL,MAAM;GACN,MAAM;GACN,KAAK;GACN,CAAC;AAEF,MAAI;AACF,SAAM,eAAe,gBAAiB,QAAQ;AAC9C,WAAQ,IAAI,kCAAkC,YAC5C,QAAQ,IAAI,UAAU,CAAC,OAAO,gCAAgC,CAC/D;WACM,OAAO;AACd,WAAQ,IAAI,0CAA0C,YACpD,QAAQ,IAAI,SAAS,CAAC,OAAO,wCAAwC,CACtE;AACD,WAAQ,MAAM,MAAM;;;CAIxB,MAAM,iBAAiB,KAAK,SAAS,QAAQ;CAC7C,MAAM,aAAa,GAAG,eAAe;CACrC,MAAM,OAAO;CACb,MAAM,YAAY,eAAe,KAAK,GAAG,GAAG,KAAK,MAAM,iBAAiB,CAAC;AAEzE,SAAQ,IAAI,kBAAkB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC3D,SAAQ,IAAI,mBAAmB,YAC7B,QAAQ,KAAK,GAAG,GAAG,MAAM,IAAI,CAAC,GAAG,GAAG,KAAK,wCAAwC,GAAG,CACrF;AACD,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,SAAQ,IAAI,wBAAwB,YAAY,QAAQ,KAAK,eAAe,CAAC;AAC7E,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,SAAQ,IAAI,qBAAqB,YAAY,QAAQ,KAAK,KAAK,YAAY,GAAG,KAAK,WAAW,GAAG,CAAC;AAClG,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,SAAQ,IAAI,iBAAiB,YAAY,QAAQ,KAAK,aAAa,GAAG,KAAK,oBAAoB,OAAO,GAAG,CAAC;AAC1G,SAAQ,IAAI,oBAAoB,YAAqB,QAAQ,KAAK,GAAG,CAAC;AACtE,SAAQ,IAAI,iBAAiB,YAAY,QAAQ,KAAK,SAAS,GAAG,KAAK,6BAA6B,GAAG,CAAC;AACxG,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;AAC7D,KAAI,WAAW;AACb,UAAQ,IAAI,uBAAuB,YACjC,QACG,IAAI,UAAU,CACd,OACC,2GACD,CACJ;AACD,UAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC;;AAE/D,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,mBAAmB,CAAC;AAC7E,SAAQ,IAAI,oBAAoB,YAAY,QAAQ,KAAK,GAAG,CAAC"}

package/dist/create/templates/nodejs/tutorial/tutorial.tsx.txt CHANGED Viewed

@@ -44,12 +44,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.flows.previewButton('apitrigger'),
     title: 'Code Preview',
-    description: () => (
-      <p>
-        Clicking on this icon will allow you to visualize the source code for a given Step. This opens a code viewer
-        with interactive feature cards that explain different parts of the code.
-      </p>
-    ),
+    description: () => <p>Clicking on this icon will allow you to visualize the source code for a given Step.</p>,
     before: [
       {
         type: 'click',
@@ -60,46 +55,142 @@ export const steps: TutorialStep[] = [
   },
   {
     elementXpath: workbenchXPath.sidebarContainer,
-    title: 'Explore the Code',
+    title: 'Step Config',
     description: () => (
       <div>
         <p>
-          The code viewer shows the Step's source code on the right. On the left, you'll find <b>feature cards</b> that
-          explain different parts of the code.
+          All Steps are defined by two main components, the <b>configuration</b> and the <b>handler</b>.
+          <br />
+          <br />
+          Let's start with the configuration, the common config attributes are
+          <i> type, name, description, and flows</i>.
+          <br />
+          <br />
         </p>
-        <br />
-        <p>
-          <b>Click on the feature cards</b> to learn about:
-        </p>
-        <ul className="square-decoration">
-          <li>
-            <b>Step Configuration</b> - Common attributes like type, name, description, and flows
-          </li>
-          <li>
-            <b>API Step Configuration</b> - HTTP method and path attributes
-          </li>
+        <ul>
           <li>
-            <b>Request Body & Response Payload</b> - Zod schemas for request/response validation
+            The <b>type</b> attribute is important since it declares the type of Step
           </li>
           <li>
-            <b>Event Driven Architecture</b> - How Steps communicate via emits and subscribes
+            The <b>flows</b> attribute will associate your Step with a given flow or set of flows.
           </li>
           <li>
-            <b>Step Handler</b> - The function that executes when the Step is triggered
-          </li>
-          <li>
-            <b>Logger</b> - Enhanced logging utilities for observability
-          </li>
-          <li>
-            <b>HTTP Response</b> - Returning responses that match your responseSchema
+            The <b>name</b> and <b>description</b> attributes will provide context in the visualization and
+            observability tools.
           </li>
         </ul>
-        <br />
-        <p>Take your time exploring these features. Click <b>Continue</b> when you're ready to move on.</p>
       </div>
     ),
-    before: [{ type: 'click', selector: workbenchXPath.flows.previewButton('apitrigger') }],
+    before: [
+      { type: 'click', selector: workbenchXPath.flows.previewButton('apitrigger') },
+      { type: 'click', selector: workbenchXPath.flows.feature('step-configuration') },
+    ],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'API Step Configuration',
+    description: () => (
+      <p>
+        There are specific configuration attributes for an API Step. Let's start with the <b>method</b> attribute. This
+        will declare the type of HTTP method used to talk to your API Step.
+        <br />
+        <br />
+        Through the <b>path</b> attribute you'll declare the url path used to trigger your API Step
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('api-configuration') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Request Body',
+    link: 'https://zod.dev/api',
+    description: () => (
+      <p>
+        The <b>bodySchema</b> attribute will define the shape of the request body.
+        <br />
+        <br />
+        <i>💡 Both the request body and response payload are defined by zod schemas</i>
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('request-body') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Response Payload',
+    link: 'https://zod.dev/api',
+    description: () => (
+      <p>
+        Through the <b>responseSchema</b> attribute you can declare the different type of http responses based on the
+        http status code.
+        <br />
+        <br />
+        <i>💡 Both the request body and response payload are defined by zod schemas</i>
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('response-payload') }],
   },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Event Driven Architecture',
+    description: () => (
+      <p>
+        Motia allows you to interact between Steps or flows through an event driven architecture.
+        <br />
+        <br />
+        In order to connect your Steps during runtime you will use the <b>emits</b> and <b>subscribes</b> attributes.
+        <br />
+        <br />
+        Through the <b>emits</b>, you can specify a list of topics that your Step emits for others to <i>subscribe</i>.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('event-driven-architecture') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Step Handler',
+    description: () => (
+      <p>
+        Now that we've covered how to declare a Step, let's dive into the <b>Step Handler</b>.<br />
+        <br />
+        Handlers are essential for the execution of your Step. For API Steps, the handler will receive the request
+        object as the first argument, followed by a second argument that provides access to the <b>logger</b>,{' '}
+        <b>event emitter</b>, <b>state manager</b>, and <b>trace id</b>.<br />
+        <br />
+        💡 We will cover these in depth further down the tutorial.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Logger',
+    description: () => (
+      <p>
+        We recommend using the provided <b>logger</b> util in order to guarantee observability through Motia's
+        ecosystem.
+        <br />
+        <br />
+        You can use logger similar to <i>console.log</i> for js or <i>print</i> for python, but with enhanced utilities,
+        such as being able to provide additional context.
+        <br />
+        <br />
+        Motia will take care of the rest to provide the best experience to visualize your logs and tie them through
+        tracing.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('logger') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'HTTP Response',
+    description: () => (
+      <p>
+        Now let's wrap our API Step and return a response.
+        <br />
+        You simply need to return an object that complies with one of the <b>responseSchema</b> definitions declared in
+        your Step configuration.
+      </p>
+    ),
     before: [{ type: 'click', selector: workbenchXPath.flows.feature('http-response') }],
   },
@@ -129,39 +220,77 @@ export const steps: TutorialStep[] = [
   },
   {
     elementXpath: workbenchXPath.sidebarContainer,
-    title: 'Explore the Event Step',
+    title: 'Event Step',
     link: 'https://www.motia.dev/docs/concepts/steps#triggers-event',
     description: () => (
-      <div>
-        <p>
-          <b>Event</b> Steps are essential for Motia's event driven architecture. They subscribe to topics and perform
-          specific tasks.
-        </p>
+      <p>
+        Now that we have an entry point in our flow, let's focus on subscribing to a <b>topic</b> and performing a
+        specific task.
+        <br /> <br />
+        For this we will look at the <b>Event</b> Step.
+        <br /> <br />
+        <b> Event</b> Steps are essential for Motia's event driven architecture. Let's dive deeper into the anatomy of
+        an Event Step by taking a look at the code visualization tool.
+        <br /> <br />
+        💡 <b>Event</b> Steps can only be triggered internally, through topic subscriptions.
+      </p>
+    ),
+    before: [
+      { type: 'click', selector: workbenchXPath.flows.previewButton('processfoodorder') },
+      { type: 'click', selector: workbenchXPath.flows.feature('step-configuration') },
+    ],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Event Step Input',
+    description: () => (
+      <p>
+        <b>Event</b> Steps, like other Steps types, are composed of a configuration and a handler.
         <br />
-        <p>
-          <b>Click on the feature cards</b> to learn about:
-        </p>
-        <ul className="square-decoration">
-          <li>
-            <b>Step Configuration</b> - Common attributes for Event Steps
-          </li>
-          <li>
-            <b>Input Schema</b> - The data structure provided by the topic (defined as a zod schema)
-          </li>
-          <li>
-            <b>Event Step Handler</b> - The handler receives topic data as the first argument
-          </li>
-          <li>
-            <b>State Management</b> - How to persist data in state with group IDs
-          </li>
-        </ul>
         <br />
-        <p>💡 <b>Event</b> Steps can only be triggered internally, through topic subscriptions.</p>
+        <b>Event</b> Steps have a specific attribute from their config, the <b>input</b> attribute, which declares the
+        data structure provided by the topic it is subscribed to.
         <br />
-        <p>Click <b>Continue</b> when you're ready to move on.</p>
-      </div>
+        <br />
+        The <b>input</b> attributes is defined as a zod schema, think of the <b>input</b> attributes as a contract for
+        other Steps that emit the topics that your Step subscribes to.
+        <br />
+        <br /> 💡 <b>Multiple Steps can subscribe to the same topic, but their input schema must be the same.</b>
+      </p>
     ),
-    before: [{ type: 'click', selector: workbenchXPath.flows.previewButton('processfoodorder') }],
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('input-schema') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Event Step Handler',
+    description: () => (
+      <p>
+        Let's take a look at the <b>Event</b> Step Handler.
+        <br />
+        <br />
+        The handler will seem familiar to other Step handlers, but notice that the first argument holds the data
+        provided for the topic or topics your Step subscribes to.
+        <br />
+        <br />
+        💡 The first argument will match the structure of your input schema, defined in the <b>Event</b> Step config.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Storing Data in State',
+    link: 'https://www.motia.dev/docs/development-guide/state-management',
+    description: () => (
+      <p>
+        Let's take a closer look at storing data in state.
+        <br />
+        <br />
+        In this example we are persisting the result of a third party HTTP request in <b>State</b>, scoping it to a
+        group id named "orders".
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('state') }],
   },
   // Cron Steps
@@ -184,34 +313,41 @@ export const steps: TutorialStep[] = [
   },
   {
     elementXpath: workbenchXPath.sidebarContainer,
-    title: 'Explore the Cron Step',
+    title: 'Cron Schedule',
     link: 'https://www.motia.dev/docs/concepts/steps#triggers-cron',
     description: () => (
-      <div>
-        <p>
-          <b>CRON</b> Steps are similar to other Step types - they have a configuration and a handler. The key difference
-          is the <b>cron</b> attribute that defines the schedule.
-        </p>
+      <p>
+        <b>CRON</b> Steps are similar to the other Step types, they are composed by a configuration and a handler.
         <br />
-        <p>
-          <b>Click on the feature cards</b> to learn about:
-        </p>
-        <ul className="square-decoration">
-          <li>
-            <b>Cron Configuration</b> - How to define the cron schedule (e.g., every 5 minutes)
-          </li>
-          <li>
-            <b>Cron Step Handler</b> - Receives only the Motia context, giving access to emit topics, log, manage state,
-            and trace ID
-          </li>
-        </ul>
         <br />
-        <p>In this example, the CRON Step evaluates orders in state and emits warnings for unprocessed orders.</p>
+        The <b>CRON</b> Step config has a distinct attribute, the <b>cron</b> attribute, through this attribute you will
+        define the cron schedule for your Step.
         <br />
-        <p>Click <b>Continue</b> when you're ready to move on.</p>
-      </div>
+        <br />
+        For instance, in this example the cron schedule is configured to execute the Step handler every 5 minutes. Let's
+        take a look at the handler definition.
+      </p>
+    ),
+    before: [
+      { type: 'click', selector: workbenchXPath.flows.previewButton('stateauditjob') },
+      { type: 'click', selector: workbenchXPath.flows.feature('cron-configuration') },
+    ],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Cron Step Handler',
+    description: () => (
+      <p>
+        The <b>CRON</b> Step handler only receives one argument, which is the Motia context, if you recall the Motia
+        context gives you access to utilities to emit <i>topics</i>, <i>log</i>, <i>manage state</i>, and it provides
+        the <i>trace id</i> associated to your Step's execution.
+        <br />
+        <br />
+        In this CRON Step example we are evaluating orders persisted in state, and emitting warnings through a topic for
+        each order that hasn't been processed and has a shipping date in the past.
+      </p>
     ),
-    before: [{ type: 'click', selector: workbenchXPath.flows.previewButton('stateauditjob') }],
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
   },
   // Endpoints

package/dist/create/templates/python/tutorial/tutorial.tsx.txt CHANGED Viewed

@@ -44,12 +44,7 @@ export const steps: TutorialStep[] = [
   {
     elementXpath: workbenchXPath.flows.previewButton('apitrigger'),
     title: 'Code Preview',
-    description: () => (
-      <p>
-        Clicking on this icon will allow you to visualize the source code for a given Step. This opens a code viewer
-        with interactive feature cards that explain different parts of the code.
-      </p>
-    ),
+    description: () => <p>Clicking on this icon will allow you to visualize the source code for a given Step.</p>,
     before: [
       {
         type: 'click',
@@ -60,46 +55,142 @@ export const steps: TutorialStep[] = [
   },
   {
     elementXpath: workbenchXPath.sidebarContainer,
-    title: 'Explore the Code',
+    title: 'Step Config',
     description: () => (
       <div>
         <p>
-          The code viewer shows the Step's source code on the right. On the left, you'll find <b>feature cards</b> that
-          explain different parts of the code.
+          All Steps are defined by two main components, the <b>configuration</b> and the <b>handler</b>.
+          <br />
+          <br />
+          Let's start with the configuration, the common config attributes are
+          <i> type, name, description, and flows</i>.
+          <br />
+          <br />
         </p>
-        <br />
-        <p>
-          <b>Click on the feature cards</b> to learn about:
-        </p>
-        <ul className="square-decoration">
-          <li>
-            <b>Step Configuration</b> - Common attributes like type, name, description, and flows
-          </li>
-          <li>
-            <b>API Step Configuration</b> - HTTP method and path attributes
-          </li>
+        <ul>
           <li>
-            <b>Request Body & Response Payload</b> - Zod schemas for request/response validation
+            The <b>type</b> attribute is important since it declares the type of Step
           </li>
           <li>
-            <b>Event Driven Architecture</b> - How Steps communicate via emits and subscribes
+            The <b>flows</b> attribute will associate your Step with a given flow or set of flows.
           </li>
           <li>
-            <b>Step Handler</b> - The function that executes when the Step is triggered
-          </li>
-          <li>
-            <b>Logger</b> - Enhanced logging utilities for observability
-          </li>
-          <li>
-            <b>HTTP Response</b> - Returning responses that match your responseSchema
+            The <b>name</b> and <b>description</b> attributes will provide context in the visualization and
+            observability tools.
           </li>
         </ul>
-        <br />
-        <p>Take your time exploring these features. Click <b>Continue</b> when you're ready to move on.</p>
       </div>
     ),
-    before: [{ type: 'click', selector: workbenchXPath.flows.previewButton('apitrigger') }],
+    before: [
+      { type: 'click', selector: workbenchXPath.flows.previewButton('apitrigger') },
+      { type: 'click', selector: workbenchXPath.flows.feature('step-configuration') },
+    ],
   },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'API Step Configuration',
+    description: () => (
+      <p>
+        There are specific configuration attributes for an API Step. Let's start with the <b>method</b> attribute. This
+        will declare the type of HTTP method used to talk to your API Step.
+        <br />
+        <br />
+        Through the <b>path</b> attribute you'll declare the url path used to trigger your API Step
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('api-configuration') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Request Body',
+    link: 'https://zod.dev/api',
+    description: () => (
+      <p>
+        The <b>bodySchema</b> attribute will define the shape of the request body.
+        <br />
+        <br />
+        <i>💡 Both the request body and response payload are defined by zod schemas</i>
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('request-body') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Response Payload',
+    link: 'https://zod.dev/api',
+    description: () => (
+      <p>
+        Through the <b>responseSchema</b> attribute you can declare the different type of http responses based on the
+        http status code.
+        <br />
+        <br />
+        <i>💡 Both the request body and response payload are defined by zod schemas</i>
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('response-payload') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Event Driven Architecture',
+    description: () => (
+      <p>
+        Motia allows you to interact between Steps or flows through an event driven architecture.
+        <br />
+        <br />
+        In order to connect your Steps during runtime you will use the <b>emits</b> and <b>subscribes</b> attributes.
+        <br />
+        <br />
+        Through the <b>emits</b>, you can specify a list of topics that your Step emits for others to <i>subscribe</i>.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('event-driven-architecture') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Step Handler',
+    description: () => (
+      <p>
+        Now that we've covered how to declare a Step, let's dive into the <b>Step Handler</b>.<br />
+        <br />
+        Handlers are essential for the execution of your Step. For API Steps, the handler will receive the request
+        object as the first argument, followed by a second argument that provides access to the <b>logger</b>,{' '}
+        <b>event emitter</b>, <b>state manager</b>, and <b>trace id</b>.<br />
+        <br />
+        💡 We will cover these in depth further down the tutorial.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Logger',
+    description: () => (
+      <p>
+        We recommend using the provided <b>logger</b> util in order to guarantee observability through Motia's
+        ecosystem.
+        <br />
+        <br />
+        You can use logger similar to <i>console.log</i> for js or <i>print</i> for python, but with enhanced utilities,
+        such as being able to provide additional context.
+        <br />
+        <br />
+        Motia will take care of the rest to provide the best experience to visualize your logs and tie them through
+        tracing.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('logger') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'HTTP Response',
+    description: () => (
+      <p>
+        Now let's wrap our API Step and return a response.
+        <br />
+        You simply need to return an object that complies with one of the <b>responseSchema</b> definitions declared in
+        your Step configuration.
+      </p>
+    ),
     before: [{ type: 'click', selector: workbenchXPath.flows.feature('http-response') }],
   },
@@ -129,39 +220,77 @@ export const steps: TutorialStep[] = [
   },
   {
     elementXpath: workbenchXPath.sidebarContainer,
-    title: 'Explore the Event Step',
+    title: 'Event Step',
     link: 'https://www.motia.dev/docs/concepts/steps#triggers-event',
     description: () => (
-      <div>
-        <p>
-          <b>Event</b> Steps are essential for Motia's event driven architecture. They subscribe to topics and perform
-          specific tasks.
-        </p>
+      <p>
+        Now that we have an entry point in our flow, let's focus on subscribing to a <b>topic</b> and performing a
+        specific task.
+        <br /> <br />
+        For this we will look at the <b>Event</b> Step.
+        <br /> <br />
+        <b> Event</b> Steps are essential for Motia's event driven architecture. Let's dive deeper into the
+        anatomy of an Event Step by taking a look at the code visualization tool.
+        <br /> <br />
+        💡 <b>Event</b> Steps can only be triggered internally, through topic subscriptions.
+      </p>
+    ),
+    before: [
+      { type: 'click', selector: workbenchXPath.flows.previewButton('processfoodorder') },
+      { type: 'click', selector: workbenchXPath.flows.feature('step-configuration') },
+    ],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Event Step Input',
+    description: () => (
+      <p>
+        <b> Event</b> Steps, like other Step types, are composed of a configuration and a handler.
         <br />
-        <p>
-          <b>Click on the feature cards</b> to learn about:
-        </p>
-        <ul className="square-decoration">
-          <li>
-            <b>Step Configuration</b> - Common attributes for Event Steps
-          </li>
-          <li>
-            <b>Input Schema</b> - The data structure provided by the topic (defined as a zod schema)
-          </li>
-          <li>
-            <b>Event Step Handler</b> - The handler receives topic data as the first argument
-          </li>
-          <li>
-            <b>State Management</b> - How to persist data in state with group IDs
-          </li>
-        </ul>
         <br />
-        <p>💡 <b>Event</b> Steps can only be triggered internally, through topic subscriptions.</p>
+        <b>Event</b> Steps have a specific attribute from their config, the <b>input</b> attribute, which declares the
+        data structure provided by the topic it is subscribed to.
         <br />
-        <p>Click <b>Continue</b> when you're ready to move on.</p>
-      </div>
+        <br />
+        The <b>input</b> attributes is defined as a zod schema, think of the <b>input</b> attributes as a contract for
+        other Steps that emit the topics that your Step subscribes to.
+        <br />
+        <br /> 💡 <b>Multiple Steps can subscribe to the same topic, but their input schema must be the same.</b>
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('input-schema') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Event Step Handler',
+    description: () => (
+      <p>
+        Let's take a look at the <b>Event</b> Step Handler.
+        <br />
+        <br />
+        The handler will seem familiar to other Step handlers, but notice that the first argument holds the data
+        provided for the topic or topics your Step subscribes to.
+        <br />
+        <br />
+        💡 The first argument will match the structure of your input schema, defined in the <b>Event</b> Step config.
+      </p>
+    ),
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Storing Data in State',
+    link: 'https://www.motia.dev/docs/development-guide/state-management',
+    description: () => (
+      <p>
+        Let's take a closer look at storing data in state.
+        <br />
+        <br />
+        In this example we are persisting the result of a third party HTTP request in <b>State</b>, scoping it to a
+        group id named "orders".
+      </p>
     ),
-    before: [{ type: 'click', selector: workbenchXPath.flows.previewButton('processfoodorder') }],
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('state') }],
   },
   // Cron Steps
@@ -184,34 +313,41 @@ export const steps: TutorialStep[] = [
   },
   {
     elementXpath: workbenchXPath.sidebarContainer,
-    title: 'Explore the Cron Step',
+    title: 'Cron Schedule',
     link: 'https://www.motia.dev/docs/concepts/steps#triggers-cron',
     description: () => (
-      <div>
-        <p>
-          <b>CRON</b> Steps are similar to other Step types - they have a configuration and a handler. The key difference
-          is the <b>cron</b> attribute that defines the schedule.
-        </p>
+      <p>
+        <b>CRON</b> Steps are similar to the other Step types, they are composed by a configuration and a handler.
         <br />
-        <p>
-          <b>Click on the feature cards</b> to learn about:
-        </p>
-        <ul className="square-decoration">
-          <li>
-            <b>Cron Configuration</b> - How to define the cron schedule (e.g., every 5 minutes)
-          </li>
-          <li>
-            <b>Cron Step Handler</b> - Receives only the Motia context, giving access to emit topics, log, manage state,
-            and trace ID
-          </li>
-        </ul>
         <br />
-        <p>In this example, the CRON Step evaluates orders in state and emits warnings for unprocessed orders.</p>
+        The <b>CRON</b> Step config has a distinct attribute, the <b>cron</b> attribute, through this attribute you will
+        define the cron schedule for your Step.
         <br />
-        <p>Click <b>Continue</b> when you're ready to move on.</p>
-      </div>
+        <br />
+        For instance, in this example the cron schedule is configured to execute the Step handler every 5 minutes. Let's
+        take a look at the handler definition.
+      </p>
+    ),
+    before: [
+      { type: 'click', selector: workbenchXPath.flows.previewButton('stateauditjob') },
+      { type: 'click', selector: workbenchXPath.flows.feature('cron-configuration') },
+    ],
+  },
+  {
+    elementXpath: workbenchXPath.sidebarContainer,
+    title: 'Cron Step Handler',
+    description: () => (
+      <p>
+        The <b>CRON</b> Step handler only receives one argument, which is the Motia context, if you recall the Motia
+        context gives you access to utilities to emit <i>topics</i>, <i>log</i>, <i>manage state</i>, and it provides
+        the <i>trace id</i> associated to your Step's execution.
+        <br />
+        <br />
+        In this CRON Step example we are evaluating orders persisted in state, and emitting warnings through a topic for
+        each order that hasn't been processed and has a shipping date in the past.
+      </p>
     ),
-    before: [{ type: 'click', selector: workbenchXPath.flows.previewButton('stateauditjob') }],
+    before: [{ type: 'click', selector: workbenchXPath.flows.feature('handler') }],
   },
   // Endpoints

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.1-beta.183-767430",
+  "version": "0.17.2-beta.184-886580",
   "license": "Elastic-2.0",
   "type": "module",
   "repository": {
@@ -46,13 +46,13 @@
     "table": "^6.9.0",
     "ts-node": "^10.9.2",
     "zod": "^4.1.12",
-    "@motiadev/adapter-bullmq-events": "0.17.1-beta.183-767430",
-    "@motiadev/adapter-redis-cron": "0.17.1-beta.183-767430",
-    "@motiadev/adapter-redis-state": "0.17.1-beta.183-767430",
-    "@motiadev/adapter-redis-streams": "0.17.1-beta.183-767430",
-    "@motiadev/core": "0.17.1-beta.183-767430",
-    "@motiadev/stream-client-node": "0.17.1-beta.183-767430",
-    "@motiadev/workbench": "0.17.1-beta.183-767430"
+    "@motiadev/adapter-bullmq-events": "0.17.2-beta.184-886580",
+    "@motiadev/adapter-redis-cron": "0.17.2-beta.184-886580",
+    "@motiadev/adapter-redis-streams": "0.17.2-beta.184-886580",
+    "@motiadev/adapter-redis-state": "0.17.2-beta.184-886580",
+    "@motiadev/core": "0.17.2-beta.184-886580",
+    "@motiadev/stream-client-node": "0.17.2-beta.184-886580",
+    "@motiadev/workbench": "0.17.2-beta.184-886580"
   },
   "devDependencies": {
     "@amplitude/analytics-types": "^2.9.2",