@superblocksteam/sdk 2.0.138 → 2.0.139-next.0

package/src/react-compiler-runtime-shim.mts

@@ -0,0 +1,50 @@
+import { createRequire } from "node:module";
+
+import type { Alias } from "vite";
+
+import { getLogger } from "./telemetry/logging.js";
+
+// Module-scoped require for resolving sibling dependencies by absolute path.
+// `createRequire` works under both the Node runtime and the Vitest module
+// runner, unlike top-level `import.meta.resolve`.
+const sdkRequire = createRequire(import.meta.url);
+const logger = getLogger();
+
+/**
+ * Vite alias mapping the React 19-only `react/compiler-runtime` specifier to
+ * the React-team `react-compiler-runtime` shim, which is API-compatible on
+ * React 17/18. Shared by the live-edit dev server and the production build so
+ * that user code (or a dependency) emitting `react/compiler-runtime` imports
+ * resolves against our React 18.3.1 runtime instead of crashing Vite
+ * resolution with `Missing "./compiler-runtime" specifier in "react" package`
+ * (APPS-2887).
+ *
+ * The exact-match string `find` fires only for `react/compiler-runtime`, never
+ * `react`, `react/jsx-runtime`, or `react-dom`.
+ *
+ * Returns `null` (and logs) if the shim package cannot be resolved — e.g. a
+ * corrupted or partial SDK install. Skipping the alias keeps the dev server /
+ * build starting for every other app instead of throwing synchronously inside
+ * `createServer()`/`build()` and permanently rejecting `vitePromise`, which
+ * would reproduce the very infinite-spinner symptom this fix removes. Only an
+ * app that actually imports `react/compiler-runtime` would then hit the
+ * original (now clearly-logged) resolution error.
+ */
+export function reactCompilerRuntimeAlias(
+  // Resolver seam: defaults to the real module resolution; overridable in tests.
+  resolve: (id: string) => string = (id) => sdkRequire.resolve(id),
+): Alias | null {
+  let replacement: string;
+  try {
+    replacement = resolve("react-compiler-runtime");
+  } catch {
+    logger.warn(
+      "[APPS-2887] Could not resolve the 'react-compiler-runtime' shim; " +
+        "skipping the react/compiler-runtime alias. Reinstall the SDK " +
+        "dependencies if an app needs it (apps that do not import " +
+        "react/compiler-runtime are unaffected).",
+    );
+    return null;
+  }
+  return { find: "react/compiler-runtime", replacement };
+}

package/src/react-compiler-runtime-shim.test.mts

@@ -0,0 +1,26 @@
+import { existsSync } from "node:fs";
+import { isAbsolute } from "node:path";
+
+import { describe, expect, it } from "vitest";
+
+import { reactCompilerRuntimeAlias } from "./react-compiler-runtime-shim.mjs";
+
+describe("reactCompilerRuntimeAlias", () => {
+  it("maps react/compiler-runtime to an existing absolute shim path", () => {
+    const alias = reactCompilerRuntimeAlias();
+    expect(alias).not.toBeNull();
+    expect(alias!.find).toBe("react/compiler-runtime");
+    expect(typeof alias!.replacement).toBe("string");
+    expect(isAbsolute(alias!.replacement as string)).toBe(true);
+    expect(existsSync(alias!.replacement as string)).toBe(true);
+  });
+
+  it("returns null instead of throwing when the shim cannot be resolved", () => {
+    // Simulate a corrupted/partial install where the shim package is absent.
+    // The dev server must keep starting (no permanently-rejected vitePromise).
+    const alias = reactCompilerRuntimeAlias(() => {
+      throw new Error("Cannot find module 'react-compiler-runtime'");
+    });
+    expect(alias).toBeNull();
+  });
+});