cabloy 5.1.234 → 5.1.236

package/.cabloy-version

@@ -1 +1 @@
-5.1.234
+5.1.236

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 5.1.236
+
+### Bug Fixes
+
+- Fix `code-inspector-plugin`.
+
+## 5.1.235
+
+### Improvements
+
+- Update the scripts documentation.
+
 ## 5.1.234
 
 ### Features

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cabloy",
-  "version": "5.1.234",
+  "version": "5.1.236",
   "gitHead": "2c5c19284bab738e492856189acb6fad74b8a7b7",
   "description": "A Node.js fullstack framework",
   "keywords": [

package/repo-docs/frontend/scripts.md

@@ -49,11 +49,11 @@ npm run build:zova:commerce:admin
 
 The `dev:zova:*` commands start the Zova development server, which uses `9000` in the Cabloy Basic default environment. Use this Zova standalone SSR entry for page, route, and hydration iteration. It may be used as Vona's development proxy target, but direct access to `9000` does not prove the Vona request boundary or integrated acceptance.
 
-## Click-to-source inspection in Cabloy Basic
+## Click-to-source inspection in Cabloy Basic and Cabloy Start
 
-Cabloy Basic enables `code-inspector-plugin` in Zova development builds. Start either `npm run dev:zova:admin` or `npm run dev:zova:web`, then open the corresponding Zova standalone SSR page. Admin and Web share the worktree's development ports; run them sequentially, not concurrently.
+Cabloy Basic and Cabloy Start enable `code-inspector-plugin` in Zova development builds. In the active edition's repository, start either `npm run dev:zova:admin` or `npm run dev:zova:web`, then open the corresponding Zova standalone SSR page. The wrappers select `cabloyBasicAdmin` / `cabloyBasicWeb` in Basic and `cabloyStartAdmin` / `cabloyStartWeb` in Start. Admin and Web share the worktree's development ports; run them sequentially, not concurrently.
 
-Hold **Option+Shift** on macOS or **Alt+Shift** on Windows/Linux, move over an element, and click to open its authored TSX location. This works with TSX in Controllers and split Render beans; it does not require converting them into Vue SFCs. Fragments have no independent DOM node, and custom-component roots may point to implementation markup rather than the caller's component tag.
+Hold **Option+Shift** on macOS or **Alt+Shift** on Windows/Linux, move over an element, and click to open its authored TSX location. This works with TSX in Controllers and split Render beans; it does not require converting them into Vue SFCs. Fragments have no independent DOM node. In both editions, instrumentation skips PascalCase and member-expression component tags and retains their native TSX descendants. This avoids passing inspector attributes to wrappers such as `ClientOnly` and `VDefaultsProvider` that have no inheritable DOM root; component invocation tags are not direct location targets.
 
 The application configuration in `zova/quasar.config.ts` uses the browser URI handler `vscode://file/{file}:{line}:{column}`. VS Code must be installed and registered for that scheme; the browser may ask for permission to open it. To use another compatible editor, change `behavior.target` to its supported URI scheme. Actual editor opening depends on that local browser/OS setup.
 

package/zova/quasar.config.ts

@@ -24,6 +24,8 @@ export default defineConfig(ctx => {
             injectTo: resolveEntry('client-entry.js'),
             match: /\.tsx$/,
             exclude: /\/\.metadata\//,
+            // Component roots may be fragments or teleports; locate their native TSX instead.
+            escapeTags: [/^[A-Z]/, /\./],
             pathType: 'absolute',
             server: 'close',
             skipSnippets: ['console'],