@specverse/engines 4.3.4 → 4.3.5

package/dist/libs/instance-factories/scaffolding/templates/generic/package-json-generator.js

@@ -50,7 +50,7 @@ function generatePackageJson(context) {
       "@playwright/test": "^1.40.0"
     };
     pkg.overrides = {
-      "esbuild": "0.27.7"
+      "esbuild": "0.25.12"
     };
   } else {
     pkg.scripts = {

package/libs/instance-factories/scaffolding/templates/generic/package-json-generator.ts

@@ -83,13 +83,17 @@ export default function generatePackageJson(context: TemplateContext): string {
     // this, tsx (backend) and vite (frontend) each pull a different
     // esbuild range, and npm's hoisting can land a JS host and native
     // binary from different patch versions in the same node_modules
-    // tree — causing `Host 0.27.7 does not match binary 0.27.1` at
-    // first `tsx watch`. Overriding forces one version down through
-    // every transitive, including the platform-specific binary
-    // (@esbuild/darwin-arm64 etc). Version tracks tsx's esbuild range
-    // since tsx runs the backend dev loop where the error surfaces.
+    // tree — causing `Host X does not match binary Y` at first
+    // `tsx watch`.
+    //
+    // Version tracks VITE's range (^0.25), not tsx's (^0.27). Vite's
+    // build step has a known destructuring-transform regression on
+    // 0.27 that triggers "Transforming destructuring to the
+    // configured target environment is not supported yet" when it
+    // emits arrow-destructured useState pairs, even for targets that
+    // natively support destructuring. tsx is tolerant of 0.25.
     pkg.overrides = {
-      'esbuild': '0.27.7',
+      'esbuild': '0.25.12',
     };
   } else {
     // Standalone mode - merge all scripts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@specverse/engines",
-  "version": "4.3.4",
+  "version": "4.3.5",
   "description": "SpecVerse toolchain — parser, inference, realize, generators, AI, registry",
   "type": "module",
   "main": "dist/index.js",