@specverse/engines 4.3.3 → 4.3.5

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.
@@ -49,6 +49,9 @@ function generatePackageJson(context) {
49
49
  pkg.devDependencies = {
50
50
  "@playwright/test": "^1.40.0"
51
51
  };
52
+ pkg.overrides = {
53
+ "esbuild": "0.25.12"
54
+ };
52
55
  } else {
53
56
  pkg.scripts = {
54
57
  ...aggregated.scripts,
@@ -78,6 +78,23 @@ export default function generatePackageJson(context: TemplateContext): string {
78
78
  pkg.devDependencies = {
79
79
  '@playwright/test': '^1.40.0',
80
80
  };
81
+
82
+ // Pin esbuild to a single version across all workspaces. Without
83
+ // this, tsx (backend) and vite (frontend) each pull a different
84
+ // esbuild range, and npm's hoisting can land a JS host and native
85
+ // binary from different patch versions in the same node_modules
86
+ // tree — causing `Host X does not match binary Y` at first
87
+ // `tsx watch`.
88
+ //
89
+ // Version tracks VITE's range (^0.25), not tsx's (^0.27). Vite's
90
+ // build step has a known destructuring-transform regression on
91
+ // 0.27 that triggers "Transforming destructuring to the
92
+ // configured target environment is not supported yet" when it
93
+ // emits arrow-destructured useState pairs, even for targets that
94
+ // natively support destructuring. tsx is tolerant of 0.25.
95
+ pkg.overrides = {
96
+ 'esbuild': '0.25.12',
97
+ };
81
98
  } else {
82
99
  // Standalone mode - merge all scripts
83
100
  pkg.scripts = {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@specverse/engines",
3
- "version": "4.3.3",
3
+ "version": "4.3.5",
4
4
  "description": "SpecVerse toolchain — parser, inference, realize, generators, AI, registry",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",