@microsoft/rayfin-guide 1.36.0 → 1.36.2

package/assets/docs/cli/environment-variables.md

@@ -73,7 +73,7 @@ The proxy is reachable wherever the Vite dev server is reachable, so keep Vite b
 The local functions setup makes these workspace changes:
 
 - Merges backend coordinates and the Node inspector argument into the configured functions package's `local.settings.json`.
-- Adds a `Functions: Attach` configuration to the root `.vscode/launch.json` after the Functions host becomes ready.
+- Adds a `Functions: Attach` configuration to the root `.vscode/launch.json` after the Functions host becomes ready. If the entry already exists and the inspector moved to another port, only its `port` is updated.
 - Leaves JSON-with-comments launch files unchanged and reports that the attach configuration must be added manually.
 - Patches recognized existing `src/services/rayfinClient.ts` and `src/services/bootstrap.ts` files once so non-adapter projects read `VITE_RAYFIN_FUNCTIONS_URL` only during Vite development.
 - Regenerates the framework `.env.local` file unless `--no-emit-env` is set.

package/assets/docs/cli/functions/dev-apply.md

@@ -68,7 +68,7 @@ If the response remains stale after compilation finishes, restart the dev sessio
 
 ## Debugging
 
-With debugging enabled (default), attach your debugger to the inspector port (`9229` by default) using the generated **"Functions: Attach"** launch configuration in VS Code. Pass `--no-debug` to run without the inspector.
+With debugging enabled (default), attach your debugger to the inspector port (`9229` by default) using the generated **"Functions: Attach"** launch configuration in VS Code. If you pass a different `--inspect-port`, the existing configuration's port is updated to match. Pass `--no-debug` to run without the inspector.
 
 ## Secrets in local development
 

package/assets/docs/cli/index.md

@@ -140,6 +140,7 @@ Other standalone subcommands and Docker maintenance flags such as `dev --stop` d
 
 Local Functions sessions show function endpoints, the debugger address, application output, and warnings or errors by default.
 Recognized host startup and configuration detail, HTTP request metadata, and successful initial build output are kept in diagnostics; use `--verbose` to mirror that detail to the terminal.
+When the host restarts after a watched file change, such as `node_modules` updates after an install, the terminal shows a single `Functions host restarted.` line and the debugger address only when it changes.
 When the initial build fails, human output includes a bounded tail of compiler output, and JSON errors include it in `buildOutput`.
 The tail retains up to 100 complete lines and 64 KiB, with an explicit marker when earlier output is omitted.
 Verbose mode does not replay the same compiler output a second time.

package/assets/docs/preview/local-dev-docker.md

@@ -48,7 +48,7 @@ The command also:
 
 - Merges local backend settings into the configured functions package's `local.settings.json`.
 - Reserves a Node inspector port starting at `9229`.
-- Adds `Functions: Attach` to the root `.vscode/launch.json` after the Functions host is ready.
+- Adds `Functions: Attach` to the root `.vscode/launch.json` after the Functions host is ready. If the entry already exists and the inspector moved to another port, only its `port` is updated.
 - Patches recognized existing `src/services/rayfinClient.ts` and `src/services/bootstrap.ts` files to pass `VITE_RAYFIN_FUNCTIONS_URL` directly only during Vite development.
 
 If `.vscode/launch.json` contains JSON with comments, Rayfin leaves it unchanged to avoid losing those comments and asks you to add the attach configuration manually.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@microsoft/rayfin-guide",
-  "version": "1.36.0",
+  "version": "1.36.2",
   "description": "Cross-cutting Builder guides for the Rayfin platform — discovered by `@microsoft/rayfin-docs` via the `rayfinDocs` package.json field convention.",
   "type": "module",
   "files": [