'PagesPageConfig' is declared but never used.

[Pnlvfx]

You're declaring this type for " legacy Pages Router pages"

but you're declaring it also on app router starting from the latest few cnaries, this will throw a typescript error because the type is unused and I have typescript configs that check for unused variables.

"next": "15.4.2-canary.50",

It wasn't happening for sure in canary.44.

type PagesPageConfig = {
default: React.ComponentType | ((props: any) => React.ReactNode | Promise<React.ReactNode> | never | void)
getStaticProps?: (context: any) => Promise | any
getStaticPaths?: (context: any) => Promise | any
getServerSideProps?: (context: any) => Promise | any
getInitialProps?: (context: any) => Promise | any
/**

• Segment configuration for legacy Pages Router pages.
• Validated at build-time by parsePagesSegmentConfig.
  */
  config?: {
  amp?: boolean | 'hybrid'
  maxDuration?: number
  runtime?: 'edge' | 'experimental-edge' | 'nodejs' | string // necessary unless config is exported as const
  regions?: string[]
  }
  }

[victormoni]

Hi @Pnlvfx

In the latest Next.js canary releases (15.4.2-canary.50 and above), a TypeScript type for legacy Pages Router pages is also being declared for the App Router.

This causes issues because:

• The type is marked but never used in App Router.
• TypeScript configs that check for unused variables throw an error.

Previously, this didn’t happen in canary.44, so it’s a recent change.

If you’re using strict TypeScript settings (like noUnusedLocals), you may start seeing errors. This happens because the type (PagesPageConfig) includes legacy properties (getStaticProps, getServerSideProps, etc.) that App Router does not use.

Workaround:

• Disable strict unused checks temporarily, or
• Wait for an official patch in the upcoming Next.js release.

References:

• Next.js Documentation
• TypeScript Compiler Options

[nazmul609]

I’m experiencing the same issue on canary.50 — PagesPageConfig is flagged as unused by TypeScript when using strict unused checks.

It seems this type is no longer referenced internally, so either it should be conditionally exported only for Pages Router, or removed entirely in App Router builds to avoid breaking stricter TS configs.

This didn’t happen in canary.44, so likely a recent regression.

[icyJoseph]

How can I try to reproduce this issue? A simple create-next-app with canaries doesn't do it. I have some idea on what problem could be happening, but I'd like to be able to replicate the issue.

[chrisweb]

I do not want to remove the include for the next.js types in the tsconfig.json, and because tsc has no exclude parameter I guess the best option right now is to ignore the two errors :/

[icyJoseph]

Yes, I forwarded the three errors to the PR author :) we'll see what resolution we end up with.

[chrisweb]

nice, thank you :)

[icyJoseph]

And a fix was merged! #82755

[Pnlvfx]

fantastic, thanks