@botonic/nx-plugin 2.25.0 → 2.27.0

package/src/generators/bot-app/files/src/server/bot/tracking.ts.template

@@ -3,16 +3,16 @@ import {
   EventAction,
   HtEventProps,
 } from '@botonic/plugin-hubtype-analytics'
-import { BotContext } from '@botonic/shared'
+import { BotonicContext } from '@botonic/shared'
 
 import { BotPlugins } from './types'
 
 export async function trackEventToHubtypeAnalytics(
-  botContext: BotContext<BotPlugins>,
+  botonicContext: BotonicContext<BotPlugins>,
   eventName: EventAction,
   args: Omit<HtEventProps, 'action'>
 ): Promise<void> {
-  const hubtypeAnalyticsPlugin = botContext.plugins.hubtypeAnalytics
+  const hubtypeAnalyticsPlugin = botonicContext.plugins.hubtypeAnalytics
   const htEventProps = {
     action: eventName,
     ...args,
@@ -27,7 +27,7 @@ export async function trackEventToHubtypeAnalytics(
   }
 
   const response = await hubtypeAnalyticsPlugin.trackEvent(
-    botContext,
+    botonicContext,
     htEventProps
   )
   console.log('TrackEvent Response', response, args)

package/src/generators/bot-app/files/src/server/lambda/handler.js.template

@@ -11,12 +11,7 @@
 import { app } from './dist/index.js'
 
 export const botonic = async (event, aws_context) => {
-  const { user_input, context } = event
-
-  await app.bot.input({
-    input: user_input || {},
-    session: context || {},
-  })
+  await app.bot.run(event)
 
   return {
     statusCode: 200,

package/src/generators/bot-app/files/vite/plugins/dev-log-viewer-html.plugin.ts.template

@@ -0,0 +1,65 @@
+import type { Plugin } from 'vite'
+
+/** Split layout + iframe for serve-bot log viewer (?logs= port). Serve-only — never applied on build. */
+const LAYOUT_STYLE = `
+.dev-layout {
+  display: flex;
+  height: 100vh;
+  margin: 0;
+  padding: 0;
+}
+.dev-layout .logs-panel {
+  flex: 1;
+  border: none;
+  border-right: 1px solid #ddd;
+}
+.dev-layout .webchat-panel {
+  flex: 1;
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  background: #f5f5f5;
+}
+`.trim()
+
+/** Runs before the inline boot script so #webchat-root exists when render runs. */
+const LAYOUT_SCRIPT = `
+document.addEventListener('DOMContentLoaded', function botonicDevLogViewerLayout() {
+  var urlParams = new URLSearchParams(window.location.search)
+  var logsPort = urlParams.get('logs')
+  if (!logsPort) return
+  document.body.innerHTML = ''
+  document.body.className = 'dev-layout'
+  var logsIframe = document.createElement('iframe')
+  logsIframe.className = 'logs-panel'
+  logsIframe.src = 'http://localhost:' + logsPort
+  var webchatPanel = document.createElement('div')
+  webchatPanel.className = 'webchat-panel'
+  webchatPanel.id = 'webchat-root'
+  document.body.appendChild(logsIframe)
+  document.body.appendChild(webchatPanel)
+})
+`.trim()
+
+export function devLogViewerIndexHtmlPlugin(): Plugin {
+  return {
+    name: 'botonic-dev-log-viewer-index-html',
+    apply: 'serve',
+    transformIndexHtml(html) {
+      const marker = '<script type="text/javascript">'
+      const pos = html.indexOf(marker)
+      if (pos === -1) {
+        return html
+      }
+
+      const styleTag = `<style data-botonic-dev-log-viewer>${LAYOUT_STYLE}</style>`
+      const scriptTag = `<script>${LAYOUT_SCRIPT}</script>`
+      const withStyle = html.replace('</head>', `${styleTag}</head>`)
+      const pos2 = withStyle.indexOf(marker)
+      if (pos2 === -1) {
+        return html
+      }
+      return `${withStyle.slice(0, pos2)}${scriptTag}${withStyle.slice(pos2)}`
+    },
+  }
+}

package/src/generators/bot-app/files/vite/webchat.config.ts.template

@@ -2,6 +2,7 @@ import { resolve } from 'path'
 import type { UserConfig } from 'vite'
 
 import { BUILD_CONFIG } from './build.config'
+import { devLogViewerIndexHtmlPlugin } from './plugins/dev-log-viewer-html.plugin'
 import { moveHtmlToRootPlugin } from './plugins/move-html.plugin'
 
 const projectRoot = resolve(__dirname, '..')
@@ -9,6 +10,11 @@ const output = BUILD_CONFIG.OUTPUT.webchat
 const server = BUILD_CONFIG.SERVER.webchat
 
 export function getWebchatConfig(command: 'serve' | 'build'): UserConfig {
+  const openPath =
+    command === 'serve' && process.env.LOG_VIEWER_PORT
+      ? `/?logs=${process.env.LOG_VIEWER_PORT}`
+      : '/'
+
   return {
     // For serve mode, use the webchat directory as root so dev server finds index.html
     // For build mode, use project root to avoid relative path issues
@@ -25,12 +31,18 @@ export function getWebchatConfig(command: 'serve' | 'build'): UserConfig {
     server: {
       port: server.port,
       host: 'localhost',
-      open: '/',
+      open: process.env.VITE_SERVE_OPEN === 'false' ? false : openPath,
+      allowedHosts: process.env.VITE_ALLOWED_HOSTS
+        ? process.env.VITE_ALLOWED_HOSTS.split(',')
+        : [],
     },
 
     preview: {
       port: server.preview,
       host: 'localhost',
+      allowedHosts: process.env.VITE_ALLOWED_HOSTS
+        ? process.env.VITE_ALLOWED_HOSTS.split(',')
+        : [],
     },
 
     build: {
@@ -52,6 +64,7 @@ export function getWebchatConfig(command: 'serve' | 'build'): UserConfig {
     },
 
     plugins: [
+      devLogViewerIndexHtmlPlugin(),
       moveHtmlToRootPlugin(projectRoot, BUILD_CONFIG.TARGET_APPS.WEBCHAT),
     ],
   }

package/src/generators/bot-app/generator.js

@@ -36,7 +36,11 @@ var import_child_process = require("child_process");
 var fs = __toESM(require("fs"));
 var path = __toESM(require("path"));
 const MODULE_DIR = __dirname;
-function getLilaraVersion() {
+function getLilaraVersion(options) {
+  const version = options.lilaraVersion;
+  if (version && version !== "latest") {
+    return version.replace(/^[\^~]/, "");
+  }
   const jsonPath = path.join(MODULE_DIR, "lilara-version.json");
   try {
     if (fs.existsSync(jsonPath)) {
@@ -280,7 +284,7 @@ function addBotonicFiles(tree, options, botonicVersion) {
 }
 async function generator_default(tree, options) {
   const botonicVersion = getBotonicVersion(options);
-  const lilaraVersion = getLilaraVersion();
+  const lilaraVersion = getLilaraVersion(options);
   const tasks = [];
   console.log(`\u{1F916} Using Botonic version: ${botonicVersion}`);
   console.log(`\u{1F3A8} Using Lilara version: ${lilaraVersion}`);

package/src/generators/bot-app/lilara-version.json

@@ -1,3 +1,3 @@
 {
-  "version": "0.4.0"
+  "version": "0.6.0"
 }

package/src/generators/bot-app/schema.d.ts

@@ -3,4 +3,5 @@ export interface BotAppGeneratorSchema {
     directory?: string;
     packageManager?: 'pnpm' | 'npm';
     botonicVersion?: string;
+    lilaraVersion?: string;
 }

package/src/generators/bot-app/schema.json

@@ -30,6 +30,10 @@
     "botonicVersion": {
       "type": "string",
       "description": "Botonic packages version. Leave empty to use the same version as the installed @botonic/nx-plugin."
+    },
+    "lilaraVersion": {
+      "type": "string",
+      "description": "Lilara packages version. Leave empty to use the version pinned by the installed generator."
     }
   },
   "required": ["name"]

package/src/generators/custom-message/files/__name__-output.ts.template

@@ -1,19 +1,21 @@
-import { BotContext } from '@botonic/core'
+import { BotonicContext } from '@botonic/core'
 import { MessageType } from '@botonic/shared'
 
 import { CUSTOM_MESSAGE_TYPES } from '../../../shared/constants'
 
-export async function <%= propertyName %>Output({ sendMessage }: BotContext) {
-  await sendMessage({
-    type: MessageType.Custom,
-    data: {
-      name: CUSTOM_MESSAGE_TYPES.<%= constantName %>,
-      props: {
-        // Add your custom props here
-        // Example: title: 'Hello from <%= className %>!'
+export async function <%= propertyName %>Output({ sendMessages }: BotonicContext) {
+  await sendMessages([
+    {
+      type: MessageType.Custom,
+      data: {
+        name: CUSTOM_MESSAGE_TYPES.<%= constantName %>,
+        props: {
+          // Add your custom props here
+          // Example: title: 'Hello from <%= className %>!'
+        },
       },
     },
-  })
+  ])
   return {
     status: 200,
     response: 'OK',

package/src/generators/custom-message/generator.js

@@ -196,7 +196,7 @@ function updateRoutes(tree, options) {
   (0, import_bot_app_utils.insertRouteBeforeFlowBuilder)(tree, options.routesPath, [
     `    {`,
     `      text: '${options.fileName}',`,
-    `      action: async () => await ${actionImport}(botContext),`,
+    `      action: async () => await ${actionImport}(botonicContext),`,
     `    },`
   ]);
 }

package/src/{cursor-commands → generators/preset/files/.claude/commands}/update-bot.md

@@ -21,7 +21,7 @@ If the `pending` array is empty, tell user: "All bot migrations are already appl
 
 ### Step 2: Discover Bots
 
-Run `bash .cursor/scripts/update-bot/discover-bots.sh` from the workspace root.
+Run `bash .claude/scripts/update-bot/discover-bots.sh` from the workspace root.
 Expected output: JSON list of bots with name, path, current version.
 
 ### Step 3: Ask Which Bot
@@ -77,13 +77,13 @@ For each pending migration (in version order, filtered to `version` ≤ target):
 
 User says: "Update my-bot"
 
-1. Read pending-bot-migrations.json → 2 entries (v2.16.0, v2.17.0), my-bot not in appliedTo for either
-2. discover-bots.sh → my-bot on v2.15.0
-3. Ask target: "Available versions: 2.16.0, 2.17.0. Update to which? [default: 2.17.0]" → user picks 2.17.0
+1. Read pending-bot-migrations.json → 2 entries (v2.0.1, v2.1.0), my-bot not in appliedTo for either
+2. discover-bots.sh → my-bot on v2.0.0
+3. Ask target: "Available versions: 2.0.1, 2.1.0. Update to which? [default: 2.1.0]" → user picks 2.1.0
 4. Branch: update/my-bot-pending-migrations
-5. Run migrate-webchat-trigger (v2.16.0) → read guide → commit → mark applied
-6. Run migrate-fix-css-code-split (v2.17.0) → no guide → commit → mark applied
-7. Report: "Done. 2 generators applied to my-bot up to v2.17.0."
+5. Run first pending generator (v2.0.1) → read guide if present → commit → mark applied
+6. Run second pending generator (v2.1.0) → commit → mark applied
+7. Report: "Done. 2 generators applied to my-bot up to v2.1.0."
 
 ### Example 2: Bot already up to date
 

package/src/{cursor-commands → generators/preset/files/.claude/commands}/update-botonic.md

@@ -45,7 +45,9 @@ If output says "no migrations to run" and `package.json` was already at the late
 <package-manager> nx migrate --run-migrations
 ```
 
-This runs workspace-level migrations and writes `.botonic/pending-bot-migrations.json` with any bot-app generators that need to be applied per bot.
+This runs any workspace-level migrations shipped by the target `@botonic/nx-plugin` version.
+
+If that version also queues bot-app generators, it may write `.botonic/pending-bot-migrations.json` for `/update-bot`.
 
 ### Step 6: Commit
 
@@ -59,5 +61,5 @@ Report:
 
 - New version installed
 - Any workspace changes applied
-- How many bot-app generators are pending in `.botonic/pending-bot-migrations.json`
-- Instruct user to run `/update-bot` to apply pending generators to each bot
+- Whether `.botonic/pending-bot-migrations.json` was created and how many generators are pending
+- If generators are pending, instruct user to run `/update-bot` to apply them per bot

package/src/{migrations/add-botonic-update-bots-skill/files/.cursor → generators/preset/files/.claude}/scripts/update-bot/discover-bots.sh

@@ -2,7 +2,7 @@
 # Discovers botonic bot apps and their current versions.
 # Uses nx show projects with tag:botonic:bot-app filter.
 # Run from workspace root. Output: JSON array of { name, path, version }.
-# Usage: bash .cursor/scripts/update-bot/discover-bots.sh
+# Usage: bash .claude/scripts/update-bot/discover-bots.sh
 
 set -euo pipefail
 

package/src/generators/preset/files/{.cursor → .claude}/skills/botonic-action/SKILL.md

@@ -44,7 +44,7 @@ Open `src/server/bot/routes.ts` and show the user the entry that was inserted:
 ```typescript
 {
   text: 'order-status',
-  action: async () => await OrderStatus(botContext),
+  action: async () => await OrderStatus(botonicContext),
 },
 ```
 
@@ -58,13 +58,13 @@ If the matcher needs changing, edit `routes.ts` directly:
 
 ```typescript
 // Regex matcher
-{ text: /^order.*/i, action: async () => await OrderStatus(botContext) },
+{ text: /^order.*/i, action: async () => await OrderStatus(botonicContext) },
 
 // Payload matcher
-{ payload: 'ORDER_STATUS', action: async () => await OrderStatus(botContext) },
+{ payload: 'ORDER_STATUS', action: async () => await OrderStatus(botonicContext) },
 
 // Message type matcher
-{ type: 'postback', payload: 'ORDER_STATUS', action: async () => await OrderStatus(botContext) },
+{ type: 'postback', payload: 'ORDER_STATUS', action: async () => await OrderStatus(botonicContext) },
 ```
 
 ### Step 4 — Ask what to implement
@@ -73,18 +73,18 @@ If not already clear from context, ask: "What should this action do?"
 
 ### Step 5 — Implement the action
 
-#### Building blocks: `sendMessage` and `BotServerMessageFactory`
+#### Building blocks: `sendMessages` and `BotServerMessageFactory`
 
-Every action receives `BotContext` as its argument. The two key pieces for sending responses are:
+Every action receives `BotonicContext` as its argument. The two key pieces for sending responses are:
 
-- **`sendMessage`** — async function from `BotContext`. Call it once per message you want to send. You can call it multiple times to send a sequence of messages.
+- **`sendMessages`** — async function from `BotonicContext`. Pass an array of messages to send them in a single call.
 - **`BotServerMessageFactory`** — imported from `@botonic/shared`. Use its factory methods to build every message; never construct raw message objects by hand.
 
 ```typescript
-import { BotContext, BotServerMessageFactory } from '@botonic/shared'
+import { BotonicContext, BotServerMessageFactory } from '@botonic/shared'
 
-export async function MyAction({ sendMessage }: BotContext) {
-  await sendMessage(BotServerMessageFactory.createText({ text: 'Hello!' }))
+export async function MyAction({ sendMessages }: BotonicContext) {
+  await sendMessages([BotServerMessageFactory.createText({ text: 'Hello!' })])
   return { status: 200, response: 'OK' }
 }
 ```
@@ -103,38 +103,38 @@ return { status: 400, response: 'Bad Request' } // validation error
 **Text message**
 
 ```typescript
-await sendMessage(BotServerMessageFactory.createText({ text: 'Your order is on the way!' }))
+await sendMessages([BotServerMessageFactory.createText({ text: 'Your order is on the way!' })])
 ```
 
 **Button message** — build each button with the appropriate factory method; never pass raw button objects
 
 ```typescript
-await sendMessage(
+await sendMessages([
   BotServerMessageFactory.createButtonMessage({
     text: 'Need help with your order?',
     buttons: [BotServerMessageFactory.createPostbackButton({ title: 'Order status', payload: 'ORDER_STATUS' }), BotServerMessageFactory.createUrlButton({ title: 'Visit website', url: 'https://example.com' }), BotServerMessageFactory.createWebviewButton({ title: 'Open form', webview: WEBVIEWS.ORDER_FORM }, session)],
-  })
-)
+  }),
+])
 ```
 
 **Custom message**
 
 ```typescript
-await sendMessage(
+await sendMessages([
   BotServerMessageFactory.createCustom({
     name: CUSTOM_MESSAGE_TYPES.ORDER_CARD,
     props: { orderId, status },
-  })
-)
+  }),
+])
 ```
 
 **Conditional logic with early return**
 
 ```typescript
-export async function OrderStatus({ sendMessage, request }: BotContext) {
+export async function OrderStatus({ sendMessages, request }: BotonicContext) {
   const { payload } = request
   if (!payload?.orderId) {
-    await sendMessage(BotServerMessageFactory.createText({ text: 'Please provide an order ID.' }))
+    await sendMessages([BotServerMessageFactory.createText({ text: 'Please provide an order ID.' })])
     return { status: 400, response: 'Bad Request' }
   }
   // fetch order and respond...
@@ -149,9 +149,9 @@ Keep HTTP calls in a dedicated service file; import and call it from the action:
 ```typescript
 import { orderService } from '../../services/order-service'
 
-export async function OrderStatus({ sendMessage, request }: BotContext) {
+export async function OrderStatus({ sendMessages, request }: BotonicContext) {
   const order = await orderService.getOrder(request.payload?.orderId)
-  await sendMessage(BotServerMessageFactory.createText({ text: order.statusMessage }))
+  await sendMessages([BotServerMessageFactory.createText({ text: order.statusMessage })])
   return { status: 200, response: 'OK' }
 }
 ```

package/src/generators/preset/files/{.cursor → .claude}/skills/botonic-custom-message/SKILL.md

@@ -105,26 +105,25 @@ export const ProductCard: React.FC<ProductCardProps> = (props: any) => {
 In the output action, build the button server-side and pass it as a prop:
 
 ```typescript
-export async function productCardOutput({ sendMessage, session }: BotContext) {
+export async function productCardOutput({ sendMessages, session }: BotonicContext) {
   const button = BotServerMessageFactory.createWebviewButton({ title: 'View details', webview: WEBVIEWS.PRODUCT }, session)
-  await sendMessage(
+  await sendMessages([
     BotServerMessageFactory.createCustom({
       name: CUSTOM_MESSAGE_TYPES.PRODUCT_CARD,
       props: { title: 'Widget Pro', price: '€9.99', button },
-    })
-  )
+    }),
+  ])
   return { status: 200, response: 'OK' }
 }
 ```
 
 #### Multiple bubbles: send multiple messages from the action
 
-`Message` always renders exactly one bubble. If the design requires multiple separate bubbles (e.g. an image bubble followed by a text bubble), send them as separate messages from the output action — do not try to nest multiple `MessageBubble` components inside one `Message`.
+`Message` always renders exactly one bubble. If the design requires multiple separate bubbles (e.g. an image bubble followed by a text bubble), pass them all in a single `sendMessages` call — do not try to nest multiple `MessageBubble` components inside one `Message`.
 
 ```typescript
 // In the output action
-await sendMessage(BotServerMessageFactory.createCustom({ name: CUSTOM_MESSAGE_TYPES.PRODUCT_IMAGE, props: { url } }))
-await sendMessage(BotServerMessageFactory.createCustom({ name: CUSTOM_MESSAGE_TYPES.PRODUCT_DETAIL, props: { title, price } }))
+await sendMessages([BotServerMessageFactory.createCustom({ name: CUSTOM_MESSAGE_TYPES.PRODUCT_IMAGE, props: { url } }), BotServerMessageFactory.createCustom({ name: CUSTOM_MESSAGE_TYPES.PRODUCT_DETAIL, props: { title, price } })])
 ```
 
 #### Styling: CSS modules only, no inline styles
@@ -185,16 +184,16 @@ Use these same tokens inside the component CSS so colours stay in sync:
 Update `<name>-output.ts` to pass the required props in `data`:
 
 ```typescript
-export async function ratingCardOutput({ sendMessage }: BotContext) {
-  await sendMessage(
+export async function ratingCardOutput({ sendMessages }: BotonicContext) {
+  await sendMessages([
     BotServerMessageFactory.createCustom({
       name: CUSTOM_MESSAGE_TYPES.RATING_CARD,
       props: {
         rating: 0,
         label: 'How was your experience?',
       },
-    })
-  )
+    }),
+  ])
   return { status: 200, response: 'OK' }
 }
 ```
@@ -208,7 +207,7 @@ The output action is already wired to a route in `routes.ts`. Call it from anoth
 ```typescript
 import { ratingCardOutput } from './rating-card-output'
 
-export async function EndConversation(ctx: BotContext) {
+export async function EndConversation(ctx: BotonicContext) {
   await ratingCardOutput(ctx)
   return { status: 200, response: 'OK' }
 }

package/src/generators/preset/files/{.cursor → .claude}/skills/botonic-webview/SKILL.md

@@ -45,11 +45,11 @@ Access request data and the close handler via `useWebviewRequest`.
 
 > **CSS loading.** `WebviewApp` (from `@botonic/webviews`) loads `@lilara/foundations` reset + tokens internally. The webview entry (`src/client/webviews/index.tsx`) only imports `@lilara/ui-web-react/styles.css` for Lilara component styles — this is generated for new bots.
 
-#### Always use UI components from `@lilara/ui-web-react`
+#### Always use UI components from `@botonic/webchat-react`
 
-Never use raw HTML elements (`<input>`, `<button>`, `<select>`, etc.) in webviews. Interactive and display primitives come from `@lilara/ui-web-react` (design system). Use `@botonic/webchat-react` only for webchat-specific pieces (e.g. `ButtonComponent` for message-style buttons).
+Never use raw HTML elements (`<input>`, `<button>`, `<select>`, etc.) in webviews. Interactive and display primitives come from `@botonic/webchat-react` (design system gateway). Never import UI components directly from `@lilara/ui-web-react` or `@lilara/ui-web` — the ESLint warn rule will flag it.
 
-The table below lists **@lilara/ui-web-react** exports (import from that package).
+The table below lists available components (import from `@botonic/webchat-react`).
 
 > **react-aria conventions.** These components are built on react-aria — prop names differ from standard HTML. Check the `.d.ts` types before using any component. Key differences: `Button` uses `onPress` not `onClick`; `Checkbox` and `Switch` use `isSelected` not `checked`, and `onChange` receives a `boolean` not an event.
 
@@ -90,7 +90,7 @@ export const OrderDetail = () => {
 **Form with submission**
 
 ```tsx
-import { Button, TextInput } from '@lilara/ui-web-react'
+import { Button, TextInput } from '@botonic/webchat-react'
 import { useWebviewRequest, WebviewBody, WebviewFrame, WebviewHeader } from '@botonic/webviews'
 
 export const BookingForm = () => {
@@ -119,7 +119,7 @@ export const BookingForm = () => {
 **Fetching data on load**
 
 ```tsx
-import { Banner, Spinner } from '@lilara/ui-web-react'
+import { Banner, Spinner } from '@botonic/webchat-react'
 import { useWebviewRequest, WebviewBody, WebviewFrame, WebviewHeader } from '@botonic/webviews'
 
 export const OrderDetail = () => {
@@ -162,12 +162,12 @@ After the webview is ready, remind the user to open it from an action using `Bot
 ```typescript
 import { WEBVIEWS } from '../../shared/constants'
 
-await sendMessage(
+await sendMessages([
   BotServerMessageFactory.createButtonMessage({
     text: 'Need to book a slot?',
     buttons: [BotServerMessageFactory.createWebviewButton({ title: 'Open form', webview: WEBVIEWS.BOOKING_FORM }, session)],
-  })
-)
+  }),
+])
 ```
 
 Use the `botonic-action` skill if the user also needs to create the triggering action.

package/src/generators/preset/files/.cursor/commands/update-bot.md

@@ -1,5 +1,3 @@
 # Update Botonic Bot
 
-Applies pending bot-app migrations from `.botonic/pending-bot-migrations.json` to a single bot.
-
-Follow the full workflow in: `node_modules/@botonic/nx-plugin/src/cursor-commands/update-bot.md`
+Follow the workflow in `.claude/commands/update-bot.md`

package/src/generators/preset/files/.cursor/commands/update-botonic.md

@@ -1,5 +1,3 @@
 # Update Botonic Workspace
 
-Updates the Botonic plugin to the latest version and queues pending bot-app migrations.
-
-Follow the full workflow in: `node_modules/@botonic/nx-plugin/src/cursor-commands/update-botonic.md`
+Follow the workflow in `.claude/commands/update-botonic.md`

package/src/lib/util/executor-helpers.d.ts

@@ -32,7 +32,6 @@ declare const TARGET_ENV_NAMES: readonly ["local", "dev", "dev2", "qa", "prod"];
 export declare function writeAppIdToEnvFile(projectRoot: string, appId: string, targetEnv: (typeof TARGET_ENV_NAMES)[number], appIdKey?: string): Promise<void>;
 /**
  * Writes or updates a single env var (key=value) in .env.[targetEnv].
- * Used e.g. for VITE_HUBTYPE_BOT_ID so the webchat auth URL uses the correct bot.
  */
 export declare function writeEnvVarToEnvFile(projectRoot: string, key: string, value: string, targetEnv: (typeof TARGET_ENV_NAMES)[number]): void;
 export declare function handleExecutorError(error: any, operation: string, showHelp?: boolean): {

package/src/lib/util/executor-helpers.js

@@ -522,15 +522,8 @@ async function performDeployLocalRuntimeWithEndpoint(context, projectRoot, endpo
         await writeAppIdToEnvFile(projectRoot, appId, resolvedTargetEnv);
       }
       botonicApiService.saveAllCredentials();
-      const botId = botonicApiService.botInfo().id;
-      writeEnvVarToEnvFile(
-        projectRoot,
-        "VITE_HUBTYPE_BOT_ID",
-        botId,
-        resolvedTargetEnv
-      );
       return {
-        botId,
+        botId: botonicApiService.botInfo().id,
         targetEnvironment,
         environmentVariables
       };

package/src/generators/bot-app-migrations/migrate-fix-css-code-split/generator.d.ts

@@ -1,5 +0,0 @@
-import type { Tree } from '@nx/devkit';
-export interface MigrateFixCssCodeSplitSchema {
-    project: string;
-}
-export default function migrateFixCssCodeSplitGenerator(tree: Tree, options: MigrateFixCssCodeSplitSchema): Promise<void>;