@tanstack/start-fn-stubs 1.161.6 → 1.162.0

package/dist/esm/createIsomorphicFn.js

@@ -1,9 +1,15 @@
 //#region src/createIsomorphicFn.ts
 function createIsomorphicFn() {
-	const fn = () => void 0;
+	return createRuntimeFn(() => void 0);
+}
+function createRuntimeFn(fn, serverImpl) {
 	return Object.assign(fn, {
-		server: () => ({ client: () => () => {} }),
-		client: () => ({ server: () => () => {} })
+		server: (nextServerImpl) => {
+			return createRuntimeFn(nextServerImpl, nextServerImpl);
+		},
+		client: (clientImpl) => {
+			return createRuntimeFn(serverImpl ?? clientImpl, serverImpl);
+		}
 	});
 }
 //#endregion

package/dist/esm/createIsomorphicFn.js.map

@@ -1 +1 @@
-{"version":3,"file":"createIsomorphicFn.js","names":[],"sources":["../../src/createIsomorphicFn.ts"],"sourcesContent":["// a function that can have different implementations on the client and server.\n// implementations not provided will default to a no-op function.\n\nexport type IsomorphicFn<\n  TArgs extends Array<any> = [],\n  TServer = undefined,\n  TClient = undefined,\n> = (...args: TArgs) => TServer | TClient\n\nexport interface ServerOnlyFn<\n  TArgs extends Array<any>,\n  TServer,\n> extends IsomorphicFn<TArgs, TServer> {\n  client: <TClient>(\n    clientImpl: (...args: TArgs) => TClient,\n  ) => IsomorphicFn<TArgs, TServer, TClient>\n}\n\nexport interface ClientOnlyFn<\n  TArgs extends Array<any>,\n  TClient,\n> extends IsomorphicFn<TArgs, undefined, TClient> {\n  server: <TServer>(\n    serverImpl: (...args: TArgs) => TServer,\n  ) => IsomorphicFn<TArgs, TServer, TClient>\n}\n\nexport interface IsomorphicFnBase {\n  server: <TArgs extends Array<any>, TServer>(\n    serverImpl: (...args: TArgs) => TServer,\n  ) => ServerOnlyFn<TArgs, TServer>\n  client: <TArgs extends Array<any>, TClient>(\n    clientImpl: (...args: TArgs) => TClient,\n  ) => ClientOnlyFn<TArgs, TClient>\n}\n\n// this is a dummy function, it will be replaced by the transformer\n// if we use `createIsomorphicFn` in this library itself, vite tries to execute it before the transformer runs\n// therefore we must return a dummy function that allows calling `server` and `client` method chains.\nexport function createIsomorphicFn(): IsomorphicFnBase {\n  const fn = () => undefined\n  return Object.assign(fn, {\n    server: () => ({ client: () => () => {} }),\n    client: () => ({ server: () => () => {} }),\n  }) as any\n}\n"],"mappings":";AAuCA,SAAgB,qBAAuC;CACrD,MAAM,WAAW,KAAA;AACjB,QAAO,OAAO,OAAO,IAAI;EACvB,eAAe,EAAE,oBAAoB,IAAI;EACzC,eAAe,EAAE,oBAAoB,IAAI;EAC1C,CAAC"}
+{"version":3,"file":"createIsomorphicFn.js","names":[],"sources":["../../src/createIsomorphicFn.ts"],"sourcesContent":["// a function that can have different implementations on the client and server.\n// implementations not provided will default to a no-op function.\n\nexport type IsomorphicFn<\n  TArgs extends Array<any> = [],\n  TServer = undefined,\n  TClient = undefined,\n> = (...args: TArgs) => TServer | TClient\n\nexport interface ServerOnlyFn<\n  TArgs extends Array<any>,\n  TServer,\n> extends IsomorphicFn<TArgs, TServer> {\n  client: <TClient>(\n    clientImpl: (...args: TArgs) => TClient,\n  ) => IsomorphicFn<TArgs, TServer, TClient>\n}\n\nexport interface ClientOnlyFn<\n  TArgs extends Array<any>,\n  TClient,\n> extends IsomorphicFn<TArgs, undefined, TClient> {\n  server: <TServer>(\n    serverImpl: (...args: TArgs) => TServer,\n  ) => IsomorphicFn<TArgs, TServer, TClient>\n}\n\nexport interface IsomorphicFnBase {\n  server: <TArgs extends Array<any>, TServer>(\n    serverImpl: (...args: TArgs) => TServer,\n  ) => ServerOnlyFn<TArgs, TServer>\n  client: <TArgs extends Array<any>, TClient>(\n    clientImpl: (...args: TArgs) => TClient,\n  ) => ClientOnlyFn<TArgs, TClient>\n}\n\n// The Start compiler normally rewrites createIsomorphicFn() chains before they\n// run. Some package tests/build steps execute this stub uncompiled though, for\n// example while Vite loads server-side modules during a build.\n//\n// In those uncompiled contexts we need a real callable fallback, not just a\n// chain-shaped object. These contexts are server-side, so once a .server()\n// implementation is registered we keep using it even if .client() is chained\n// later. Client bundles still get the correct client/no-op implementation\n// because the compiler rewrites the original call chain before runtime.\nexport function createIsomorphicFn(): IsomorphicFnBase {\n  return createRuntimeFn(() => undefined) as any\n}\n\ntype RuntimeFallbackFn = (() => any) & {\n  server: (serverImpl: () => any) => RuntimeFallbackFn\n  client: (clientImpl: () => any) => RuntimeFallbackFn\n}\n\nfunction createRuntimeFn(\n  fn: () => any,\n  serverImpl?: () => any,\n): RuntimeFallbackFn {\n  return Object.assign(fn, {\n    server: (nextServerImpl: () => any) => {\n      return createRuntimeFn(nextServerImpl, nextServerImpl)\n    },\n    client: (clientImpl: () => any) => {\n      return createRuntimeFn(serverImpl ?? clientImpl, serverImpl)\n    },\n  })\n}\n"],"mappings":";AA6CA,SAAgB,qBAAuC;AACrD,QAAO,sBAAsB,KAAA,EAAU;;AAQzC,SAAS,gBACP,IACA,YACmB;AACnB,QAAO,OAAO,OAAO,IAAI;EACvB,SAAS,mBAA8B;AACrC,UAAO,gBAAgB,gBAAgB,eAAe;;EAExD,SAAS,eAA0B;AACjC,UAAO,gBAAgB,cAAc,YAAY,WAAW;;EAE/D,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tanstack/start-fn-stubs",
-  "version": "1.161.6",
+  "version": "1.162.0",
   "description": "Stub functions for TanStack Start isomorphic and environment-specific functions",
   "author": "Tanner Linsley",
   "license": "MIT",
@@ -50,12 +50,12 @@
     "test:unit:dev": "vitest --watch",
     "test:eslint": "eslint ./src",
     "test:types": "pnpm run \"/^test:types:ts[0-9]{2}$/\"",
-    "test:types:ts54": "node ../../node_modules/typescript54/lib/tsc.js",
     "test:types:ts55": "node ../../node_modules/typescript55/lib/tsc.js",
     "test:types:ts56": "node ../../node_modules/typescript56/lib/tsc.js",
     "test:types:ts57": "node ../../node_modules/typescript57/lib/tsc.js",
     "test:types:ts58": "node ../../node_modules/typescript58/lib/tsc.js",
-    "test:types:ts59": "tsc",
+    "test:types:ts59": "node ../../node_modules/typescript59/lib/tsc.js",
+    "test:types:ts60": "tsc",
     "test:build": "publint --strict && attw --ignore-rules no-resolution --pack .",
     "build": "vite build"
   }

package/src/createIsomorphicFn.ts

@@ -34,13 +34,34 @@ export interface IsomorphicFnBase {
   ) => ClientOnlyFn<TArgs, TClient>
 }
 
-// this is a dummy function, it will be replaced by the transformer
-// if we use `createIsomorphicFn` in this library itself, vite tries to execute it before the transformer runs
-// therefore we must return a dummy function that allows calling `server` and `client` method chains.
+// The Start compiler normally rewrites createIsomorphicFn() chains before they
+// run. Some package tests/build steps execute this stub uncompiled though, for
+// example while Vite loads server-side modules during a build.
+//
+// In those uncompiled contexts we need a real callable fallback, not just a
+// chain-shaped object. These contexts are server-side, so once a .server()
+// implementation is registered we keep using it even if .client() is chained
+// later. Client bundles still get the correct client/no-op implementation
+// because the compiler rewrites the original call chain before runtime.
 export function createIsomorphicFn(): IsomorphicFnBase {
-  const fn = () => undefined
+  return createRuntimeFn(() => undefined) as any
+}
+
+type RuntimeFallbackFn = (() => any) & {
+  server: (serverImpl: () => any) => RuntimeFallbackFn
+  client: (clientImpl: () => any) => RuntimeFallbackFn
+}
+
+function createRuntimeFn(
+  fn: () => any,
+  serverImpl?: () => any,
+): RuntimeFallbackFn {
   return Object.assign(fn, {
-    server: () => ({ client: () => () => {} }),
-    client: () => ({ server: () => () => {} }),
-  }) as any
+    server: (nextServerImpl: () => any) => {
+      return createRuntimeFn(nextServerImpl, nextServerImpl)
+    },
+    client: (clientImpl: () => any) => {
+      return createRuntimeFn(serverImpl ?? clientImpl, serverImpl)
+    },
+  })
 }