How to call action with middleware without schema

[aymericfontaine]

Hi 👋

I am in the process of migrating a project from version 6 to version 7. I am encountering a compilation error when building my project related to an action without a schema.

Can you help me identify what I might have missed?

Thank you

const action = createSafeActionClient({
...
}).use(async ({ next }) => {
  const session = await auth();
  return next({ ctx: { user: session?.user } });
});

export const authAction = action.use(async ({ next, ctx }) => {
  if (!ctx.user) throw new ActionUnauthorizedError();
  return next({ ctx: { user: ctx.user } });
});

// no schema specified
export const getWallets = authAction.action(async ({ ctx: { user } }) => {
 return await prisma.wallet.findMany({
    where: {
      userId: user.id,
    }
  });
});

export default async function Page() {
  const wallets = await getWallets();

  if (!wallets?.data) {
    redirect("/");
  }

  ...

Type error: Expected 1 arguments, but got 0.
Expected first argument of getWallets() is "input: void"

[TheEdoRan]

Well, that's pretty weird. Type void means that you don't need to provide an argument, so it's correct. What's even weirder is that I've just tried to compile a Next.js project with your same action setup and got no compilation errors:

Calling it in a client component page with no arguments:

And here's the action client file:

[aymericfontaine]

Thank you for the feedback. It is indeed strange. My VSCode does not show any errors, but it does not compile during the build. I have the same problem when deploying on Vercel.

The solution I found is to send undefined as a parameter.

[TheEdoRan]

If you can reproduce it in a new repo/project, please provide a link to it so I can investigate this issue, because that's very weird. Never seen that happen before. Thanks!

[aymericfontaine]

Hey @TheEdoRan, my issue was due to a TypeScript version >= 5.5.2
The latest experimental version (#180 (comment)) fixes the problem 👍