Incompatible with next-safe-action

[LubomirGeorgiev]

I am trying to use https://github.com/next-safe-action/next-safe-action with Vinext but I am getting this error

12:21:32 AM [vite] Internal server error: unsupported non async function
  Plugin: rsc:use-server
  File: /Users/[USER]/projects/vinext-nextjs/src/test.action.ts:5:0
  1  |  "use server";
  2  |  import { actionClient } from "./lib/safe-action";
  3  |  export const testAction = actionClient.action(async () => {
     |  ^
  4  |          return { message: "Hello, world!" };
  5  |  });

Steps to reproduce

1. Clone https://github.com/LubomirGeorgiev/vinext-next-safe-action
2. Run pnpm dev:vinext

[southpolesteve]

I think this might be a broader issue. Put up what I think fixes here: #731

Root cause was that @vitejs/plugin-rsc rejects file-level "use server" exports when the exported value is a wrapped async action, for example:

"use server";
export const testAction = actionClient.action(async () => { ... });

[southpolesteve]

@hi-ogawa any insight from the @vitejs/plugin-rsc perspective? I wonder if this is actually better fixed there

Background:

• vite-plugin-react issue #618
• That appears to have relaxed the wrap-export path.
• But I’m still seeing a failure today with @vitejs/plugin-rsc 0.5.21 on what looks like the client proxy path.

Repro shape:

"use server";

export const testAction = actionClient.action(async () => {
  return { message: "Hello, world!" };
});

[hi-ogawa]

That's what vitejs/vite-plugin-react#754 is intended to allow, so if not, it's likely a bug.

[james-elicx]

That's what vitejs/vite-plugin-react#754 is intended to allow, so if not, it's likely a bug.

I've just been looking through this, and it seems that differs from the proxy-export.ts file, so I've put up a PR to align them with the thought that it might fix the issue.