[BUG] TypeScript issue with parsedInput in useAction Hook

[hadrysm]

Are you using the latest version of this library?

• I verified that the issue exists in the latest next-safe-action release

Is there an existing issue for this?

• I have searched the existing issues and found nothing that matches

Describe the bug

Hi, I encountered a TypeScript error. The type for my object, which I am validating using zod, is always any.

Reproduction steps

My action with zod:

"use server";
import { createSafeActionClient } from "next-safe-action";
import { z } from "zod";
import { db } from "~/server/db";
import { feedbacks } from "~/server/db/schema";

const action = createSafeActionClient();

const createFeedbackSchema = z.object({
  message: z
    .string()
    .min(10, {
      message: "Message must be at least 10 characters.",
    })
    .max(256, {
      message: "Message must not be longer than 256 characters.",
    }),
});

export const myCallback = action
  .schema(createFeedbackSchema)
  .action(async ({ parsedInput: { message } }) => {
    await db.insert(feedbacks).values({ message, userId: "user-id" });

    return {
      message: "Thank you! Your message has been sent.",
    };
  });

parsedInput is of type any:

The same issue occurs in the component where I use the useAction hook:

Expected behavior

My type for parsedInput should be:

 interface Input {
    message: string;
  }

Minimal reproduction example

See reproduction steps

Operating System

macOs

Library version

7.0.2

Next.js version

14.2.1

Additional context

No response

[TheEdoRan]

Need a link to a repo with a minimal reproduction example, thanks.

[vidforstner]

Hi, I'm running into the same issue on Windows.

Here is a minimal reproduction example

[coreybain]

was having the same issue - check VS code is using your workspace typescript version not the editors - that fixed it for me

[TheEdoRan]

@vidforstner thanks for the link. However, I can't reproduce the issue:

As @coreybain already said, this could be caused by a TypeScript version mismatch, see:

• [BUG] parsedInput not being automatically typed #170

[laurent512]

Strange, I also have some typescript issues, but related to destructuring the result of an action

[TheEdoRan]

@laurent512 is this the same issue as #175?

[TheEdoRan]

@hadrysm If this is related to TS 5.5.2 can we close this issue in favor of this other one?

• [BUG] Not compatible with Typescript >= 5.5.2 #180

[TheEdoRan]

https://next-safe-action.dev/docs/troubleshooting#schema-and-parsedinput-are-typed-any-broken-types-and-build-issues