next.js: Next 13: Missing Types for generateStaticParams

@thaddeuscleo I have got it now: params and if necessary searchParams must be declared as optional, then the compiler does not complain anymore.

-  searchParams: { currentPage: number };
+  searchParams?: { currentPage: number };

With it also own separately declared props types work.

I’m currently running "next": "^13.0.3" and i still facing same issue when executing npm run build. this line of code cause the build to fail:

export default async function RoomDashboard({
  searchParams,
}: {
  searchParams: { currentPage: number };
}) {
   // page logic
}

This is the error when executing npm run build:

Type error: Page "app/room/page.tsx" does not match the required types of a Next.js Page.
  Invalid configuration:
    The exported page component isn't correctly typed.
        Expected "{ searchParams: { currentPage: number; }; }", got "PageProps".

I didn’t face any problem during dev(npm run dev), I’m not sure whether it’s my fault or the feature got some bugs during build time.

NextJS 13 is dope 🚀 , but there is something can be polish. thank you Nextjs Dev member have a nice day 😄. I really hope this can be sort out soon…

I’m facing the same problem during build:

type PageParams = {
  slug: string;
};

type PageProps = {
  params: PageParams;
};

export const dynamicParams = true;

export async function generateStaticParams(): Promise<PageParams[]> {
  const payload = await getNodes();

  return payload.nodes.map((node) => ({
    slug: node.path
  }));
}

export default async function NodePage({ params }: PageProps) {
  const node = await getNode(params.slug);
  if (!node) return notFound();
  return (
    <div>
      <h1>Hello, Next.js! {params.slug}</h1>
      <pre>{JSON.stringify({ node }, null, 2)}</pre>
    </div>
  );
}

...
info  - Compiled successfully
info  - Linting and checking validity of types ...Failed to compile.

Type error: Page "app/[slug]/page.tsx" does not match the required types of a Next.js Page.
  Invalid configuration:
    The exported page component isn't correctly typed.
          Invalid configuration:
            Expected "{ slug: string; } | undefined", got "PageParams | undefined".

@shuding Any news on this? This is preventing me from deploying.

@shuding I still seem to be getting this error. Here is the result of running next build

Here is the file it is failing at https://github.com/gabrielgrover/improved-octo-spoon/blob/main/app/blog/[slug]/page.tsx

@gabrielgrover We already released 13.0.1, let us know if the issue is still happening!

This is still happening for me on Next 13.1.4, only during next build:

Type error: Page "app/[username]/[storySlug]/page.js" does not match the required types of a Next.js Page.
  Invalid configuration:
    The exported Page component isn't correctly typed.
        Expected "{ params: any; searchParams: any; }", got "PageProps".

app/[username]/[storySlug]/page.js

async function StoryPage({ params, searchParams }) {
  ...
}

export default StoryPage;

Changing it to the following causes the error to not happen:

app/[username]/[storySlug]/page.js

async function StoryPage(props) {
  const { params, searchParams } = props;
  ...
}

export default StoryPage;

the perfect fix It worked 😃 thank you

This is still happening for me on Next 13.1.4, only during next build:

Type error: Page "app/[username]/[storySlug]/page.js" does not match the required types of a Next.js Page.
  Invalid configuration:
    The exported Page component isn't correctly typed.
        Expected "{ params: any; searchParams: any; }", got "PageProps".

app/[username]/[storySlug]/page.js

async function StoryPage({ params, searchParams }) {
  ...
}

export default StoryPage;

Changing it to the following causes the error to not happen:

app/[username]/[storySlug]/page.js

async function StoryPage(props) {
  const { params, searchParams } = props;
  ...
}

export default StoryPage;

After updating to 13.0.1, I was still facing the issue. However, I fixed it by updating the page’s type from NextPage to FC.