⚠️ Potential issue | 🟠 Major

find . -name "package.json" -path "*/apps/desktop/*" | head -5

cat apps/desktop/package.json | grep -A2 -B2 '"postinstall"'
cat apps/desktop/package.json | grep -A2 -B2 '"trpc-electron"'
find . -name "patch-trpc-electron.ts" -type f

#!/bin/bash
echo "=== Checking postinstall script ===" 
cat apps/desktop/package.json | grep -A1 '"postinstall"'

echo -e "\n=== Checking trpc-electron version ===" 
cat apps/desktop/package.json | grep -A1 '"trpc-electron"'

echo -e "\n=== Finding patch script ===" 
find . -name "patch-trpc-electron.ts" -type f

#!/bin/bash
# Find and display the patch script
if [ -f "scripts/patch-trpc-electron.ts" ]; then
  echo "=== Patch script content ===" 
  cat scripts/patch-trpc-electron.ts
else
  echo "Finding patch script..."
  find . -name "*patch*trpc*" -type f 2>/dev/null | head -10
fi

cat apps/desktop/package.json | jq '.scripts.postinstall, .dependencies."trpc-electron", .devDependencies."trpc-electron"' | head -20

cat scripts/patch-trpc-electron.ts | head -100

cat apps/desktop/scripts/patch-trpc-electron.ts

cat ./apps/desktop/scripts/patch-trpc-electron.ts

head -150 apps/desktop/scripts/patch-trpc-electron.ts

Pin trpc-electron to an exact version to prevent silent patch failures.

The postinstall script patches trpc-electron using fragile regex patterns that depend on specific code structure and minification artifacts (e.g., function names like Fe, ke). These patterns target three locations: the source TypeScript file, ESM dist, and minified CJS dist. With caret versioning (^0.1.2), any patch/minor release of trpc-electron could change its code structure or minification scheme, causing the patches to silently fail to apply (the script only logs but doesn't error on failed matches). This leaves the app running with an unpatched dependency that will break on Node.js 22+ or Electron 39+.

Change to exact version pinning:

"trpc-electron": "0.1.2"

Revert to caret versioning only after trpc-electron provides an upstream fix for Symbol.asyncDispose compatibility.

In apps/desktop/package.json around line 19, the trpc-electron dependency is
caret-pinned which allows minor/patch upgrades that can change minified output
and cause the fragile postinstall patch script to silently fail; change the
dependency entry to an exact version string "0.1.2" (remove the ^) and update
the project lockfile (bun.lockb / lockfile if present) so installs are
deterministic; keep this exact pin until trpc-electron publishes an upstream
compatibility fix for Symbol.asyncDispose, then revert to caret if desired.

⚠️ Potential issue | 🟠 Major

Add validation to detect when patches fail to apply.

The regex pattern is extremely brittle and depends on exact formatting, variable names (it), comment text, and error messages. If trpc-electron updates its code, the regex will silently fail to match, and the runtime error will reoccur.

 const utilsPath = join(trpcElectronPath, "src", "main", "utils.ts");
 if (existsSync(utilsPath)) {
 	let content = readFileSync(utilsPath, "utf-8");
 	const originalContent = content;
 
+	// Check if already patched
+	const isAlreadyPatched = !content.includes("Symbol.asyncDispose already exists");
+	const needsPatch = content.includes("Symbol.asyncDispose already exists");
+
 	// Remove the check that throws when Symbol.asyncDispose exists
 	content = content.replace(
 		/\/\/ eslint-disable-next-line no-restricted-syntax\s*\n\s*if \(it\[Symbol\.asyncDispose\]\) \{\s*\n\s*throw new Error\('Symbol\.asyncDispose already exists'\);\s*\n\s*\}\s*\n/,
 		"// Node.js 22+ / Electron 39+ has Symbol.asyncDispose built-in on AsyncIterators\n  // We overwrite it with our custom dispose function\n"
 	);
 
 	if (content !== originalContent) {
 		writeFileSync(utilsPath, content);
 		console.log("Patched trpc-electron/src/main/utils.ts");
+	} else if (needsPatch) {
+		console.error("ERROR: Failed to patch trpc-electron/src/main/utils.ts - regex pattern may be outdated");
+		process.exit(1);
 	}
 }

In apps/desktop/scripts/patch-trpc-electron.ts around lines 23 to 39, the
brittle regex replacement may silently fail if upstream formatting or names
change; add explicit validation after attempting the replace: detect whether the
content changed or already contains the intended replacement, and if neither is
true throw or log a failing error and exit (or fail the CI) so the developer is
alerted; apply the same pattern of validation to the subsequent dist file
patches (lines ~41-75) to ensure each patch either applied or was already
present before writing files.

we should possibly fork electron-trpc and add it as a package in our repo - it's no longer maintained so we probably will have to do similar stuff to make it work :/