@archie/devtools 0.1.6 → 0.1.7

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.
@@ -10130,7 +10130,7 @@ function isPreviewOrigin(origin) {
10130
10130
  var DEFAULT_SCRIPT_ID = "archie-inspector-script";
10131
10131
  var R2_INSPECTOR_BASE_URL = "https://pub-bf238c278d9644b39ec34ecaca1d315c.r2.dev";
10132
10132
  function readBuildVersion() {
10133
- return "0.1.6" ? "0.1.6" : null;
10133
+ return "0.1.7" ? "0.1.7" : null;
10134
10134
  }
10135
10135
  var REMOTE_INSPECTOR_VERSION = readBuildVersion();
10136
10136
  var isRemoteInspectorUrlVersioned = REMOTE_INSPECTOR_VERSION !== null;
@@ -10095,7 +10095,7 @@ function isPreviewOrigin(origin) {
10095
10095
  var DEFAULT_SCRIPT_ID = "archie-inspector-script";
10096
10096
  var R2_INSPECTOR_BASE_URL = "https://pub-bf238c278d9644b39ec34ecaca1d315c.r2.dev";
10097
10097
  function readBuildVersion() {
10098
- return "0.1.6" ? "0.1.6" : null;
10098
+ return "0.1.7" ? "0.1.7" : null;
10099
10099
  }
10100
10100
  var REMOTE_INSPECTOR_VERSION = readBuildVersion();
10101
10101
  var isRemoteInspectorUrlVersioned = REMOTE_INSPECTOR_VERSION !== null;
@@ -4123,6 +4123,30 @@
4123
4123
  )
4124
4124
  }
4125
4125
 
4126
+ // Same "usage outranks kit template" precedence as
4127
+ // `getInspectorInfoFromElement`/`getExactSourceSignatureFromElement`
4128
+ // (see those docstrings) — `extractMetadata`'s `editorMeta`/`vid`/
4129
+ // `nodeMeta` used to read plain `findNearestEditorMeta`, which walks
4130
+ // the fiber chain nearest-meta-wins with NO usage projection. That is
4131
+ // correct for a bare, directly-authored node, but wrong the moment
4132
+ // `element` is a kit-rendered host with its OWN kit-template direct
4133
+ // meta (Kit.Card's root div, a real, instrumented `origin:'kit'`/
4134
+ // `template:true` position) — it reported the TEMPLATE's own internal
4135
+ // vid instead of the screen-file USAGE's, the instant the bare-wrapper
4136
+ // guard above (or any other caller) hands `extractMetadata` a
4137
+ // kit-rendered node directly, instead of one already climbed past by
4138
+ // `climbVisualUnitChain`'s kit-wrapper fallback.
4139
+ function resolveEditorMetaResultForElement(element) {
4140
+ if (!element) return null
4141
+ var usageMeta = projectUsageMetaFromElement(element)
4142
+ if (usageMeta) return { meta: usageMeta, element: element }
4143
+ var directMeta = getDirectEditorMetaFromElement(element)
4144
+ if (directMeta) return { meta: directMeta, element: element }
4145
+ var ownerMeta = getOwnerEditorMetaFromElement(element)
4146
+ if (ownerMeta) return { meta: ownerMeta, element: element }
4147
+ return findNearestEditorMeta(element)
4148
+ }
4149
+
4126
4150
  function extractMetadata(element) {
4127
4151
  if (!element) return null
4128
4152
 
@@ -4138,7 +4162,7 @@
4138
4162
  }
4139
4163
 
4140
4164
  const inspectorInfo = getInspectorInfoFromElement(element)
4141
- const editorMeta = findNearestEditorMeta(element)
4165
+ const editorMeta = resolveEditorMetaResultForElement(element)
4142
4166
 
4143
4167
  return {
4144
4168
  tagName: tagName,
@@ -4123,6 +4123,30 @@
4123
4123
  )
4124
4124
  }
4125
4125
 
4126
+ // Same "usage outranks kit template" precedence as
4127
+ // `getInspectorInfoFromElement`/`getExactSourceSignatureFromElement`
4128
+ // (see those docstrings) — `extractMetadata`'s `editorMeta`/`vid`/
4129
+ // `nodeMeta` used to read plain `findNearestEditorMeta`, which walks
4130
+ // the fiber chain nearest-meta-wins with NO usage projection. That is
4131
+ // correct for a bare, directly-authored node, but wrong the moment
4132
+ // `element` is a kit-rendered host with its OWN kit-template direct
4133
+ // meta (Kit.Card's root div, a real, instrumented `origin:'kit'`/
4134
+ // `template:true` position) — it reported the TEMPLATE's own internal
4135
+ // vid instead of the screen-file USAGE's, the instant the bare-wrapper
4136
+ // guard above (or any other caller) hands `extractMetadata` a
4137
+ // kit-rendered node directly, instead of one already climbed past by
4138
+ // `climbVisualUnitChain`'s kit-wrapper fallback.
4139
+ function resolveEditorMetaResultForElement(element) {
4140
+ if (!element) return null
4141
+ var usageMeta = projectUsageMetaFromElement(element)
4142
+ if (usageMeta) return { meta: usageMeta, element: element }
4143
+ var directMeta = getDirectEditorMetaFromElement(element)
4144
+ if (directMeta) return { meta: directMeta, element: element }
4145
+ var ownerMeta = getOwnerEditorMetaFromElement(element)
4146
+ if (ownerMeta) return { meta: ownerMeta, element: element }
4147
+ return findNearestEditorMeta(element)
4148
+ }
4149
+
4126
4150
  function extractMetadata(element) {
4127
4151
  if (!element) return null
4128
4152
 
@@ -4138,7 +4162,7 @@
4138
4162
  }
4139
4163
 
4140
4164
  const inspectorInfo = getInspectorInfoFromElement(element)
4141
- const editorMeta = findNearestEditorMeta(element)
4165
+ const editorMeta = resolveEditorMetaResultForElement(element)
4142
4166
 
4143
4167
  return {
4144
4168
  tagName: tagName,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@archie/devtools",
3
- "version": "0.1.6",
3
+ "version": "0.1.7",
4
4
  "description": "DevTools for Archie generated applications - Route synchronization and editor communication",
5
5
  "sideEffects": false,
6
6
  "repository": {