@volter/editor-react 0.5.71 → 0.5.72
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.
- package/package.json +3 -3
- package/serving/ui-oid-plugin.ts +3 -3
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "@volter/editor-react",
|
|
3
3
|
"author": "Volter AI, Inc.",
|
|
4
4
|
"license": "AGPL-3.0-only",
|
|
5
|
-
"version": "0.5.
|
|
5
|
+
"version": "0.5.72",
|
|
6
6
|
"publishConfig": {
|
|
7
7
|
"access": "public"
|
|
8
8
|
},
|
|
@@ -38,8 +38,8 @@
|
|
|
38
38
|
"serving": "./dist-node/serving.mjs"
|
|
39
39
|
},
|
|
40
40
|
"dependencies": {
|
|
41
|
-
"@volter/editor-sdk": "0.5.
|
|
42
|
-
"@volter/editor-project": "0.5.
|
|
41
|
+
"@volter/editor-sdk": "0.5.72",
|
|
42
|
+
"@volter/editor-project": "0.5.72",
|
|
43
43
|
"typescript": "5.9.3"
|
|
44
44
|
},
|
|
45
45
|
"peerDependencies": {
|
package/serving/ui-oid-plugin.ts
CHANGED
|
@@ -19,13 +19,13 @@
|
|
|
19
19
|
* dev-server `fs.allow` pipeline `server/dev.ts` already builds for project scripts
|
|
20
20
|
* (T3.3) — so `ReactRootAuthoringAdapter` needs those files instrumented too.
|
|
21
21
|
* `defaultProjectScopeInclude` widens to PROJECT scope, not repo-global: any `.tsx`
|
|
22
|
-
* file outside `node_modules`, EXCEPT the
|
|
22
|
+
* file outside `node_modules`, EXCEPT the Volter tooling/engine source trees this repo
|
|
23
23
|
* itself is built from (`packages/engine/src`, `packages/create-volter-project`,
|
|
24
24
|
* `packages/volter-cli`, `packages/editor-sdk`, and `packages/editor/src` generally —
|
|
25
25
|
* carving OUT `ui-editor/editable-components` so the existing UI-edit-mode surface
|
|
26
26
|
* keeps working unchanged). This does NOT depend on which project happens to be
|
|
27
27
|
* open — `fs.allow` already bounds what Vite can even reach, and this predicate
|
|
28
|
-
* additionally keeps the
|
|
28
|
+
* additionally keeps the Volter app's OWN react source un-instrumented.
|
|
29
29
|
*
|
|
30
30
|
* Vendored trees: a vendored GAME's source is STAMPED; every other `/vendor/`
|
|
31
31
|
* tree is not. `data-oid` stamping is what makes a `.tsx` file addressable —
|
|
@@ -236,7 +236,7 @@ function nearestManifestExcludesIngestReact(dir: string): boolean {
|
|
|
236
236
|
* Cap 2 (React visual-edit parity): the scope guard for the `/__ui-source/css` endpoint.
|
|
237
237
|
* A CSS file path (from a stylesheet's `data-vite-dev-id`) is editable iff it is a
|
|
238
238
|
* first-party PROJECT `.css` file — same carve-outs as `defaultProjectScopeInclude`
|
|
239
|
-
* (never node_modules, vendored trees, the
|
|
239
|
+
* (never node_modules, vendored trees, the Volter tooling/engine source, or the editor's
|
|
240
240
|
* own source). Paths are normalized to forward slashes so a Windows dev-id matches. This
|
|
241
241
|
* is the CSS analogue of the `.tsx` stamping scope: an out-of-scope path must not become
|
|
242
242
|
* writable through a client-supplied `file`.
|