Turbopack Error: "Failed to find Server Action" when passing re-exported server actions from RSC to Client Components

### Link to the code that reproduces this issue https://github.com/ryanburns23/failed-to-find-server-action ### To Reproduce 1. Start the reproduction project using: `next dev --turbopack` 2. Click the button which triggers a server action passed as a prop from a RSC to a client component. 3. Observe the error message in the terminal: `Error: Failed to find Server Action` ### Current vs. Expected behavior Current Behavior: When calling the `logAction()` server action, a terminal error appears: `Error: Failed to find Server Action`. Expected Behavior: The server action (`logAction()`) should execute normally without the error message. ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020 Available memory (MB): 98304 Available CPU cores: 12 Binaries: Node: 22.13.0 npm: 10.9.2 Yarn: N/A pnpm: 10.6.2 Relevant Packages: next: 15.4.0-canary.9 // Latest available version is detected (15.4.0-canary.9). eslint-config-next: N/A react: 19.1.0 react-dom: 19.1.0 typescript: 5.8.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Server Actions, Turbopack ### Which stage(s) are affected? (Select all that apply) next dev (local) ### Additional context - The reproduction illustrates the issue occurs when a server action is re-exported from another file (`lib.ts`). Specifically, the current setup in `actions.ts` looks like this: ```ts "use server"; import { log } from "./lib"; export { log as logAction }; ``` - Defining `logAction()` directly within `actions.ts` (with `"use server"` at the top) prevents the issue. - Importing the server action directly from the logger client component also resolves the issue. - The issue does not occur when running without Turbopack (i.e., without the `--turbopack` flag). If testing without Turbopack, you may need to delete the `.next` f…