Cannot obtain slugs in api routes while using Typescript

Checklist

[X] The issue can be reproduced in the nextjs-auth0 sample app (or N/A).
[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description

Following the NextJS documentation for app router Dynamic Route Segments, the Typescript compiler will produce build errors when executing next build.

Switching the route file to compile in JavaScript, route slug is populated as expected.

Reproduction

file: /app/api/test/[slug]/route.ts route: /api/test/aaaaa

expect TypeScript to compile and the slug parameter to be populated with 'aaaaa'

import { withApiAuthRequired } from '@auth0/nextjs-auth0';
import { NextRequest, NextResponse } from 'next/server';

interface GetParams {
  params: { slug: string };
}

export const GET = withApiAuthRequired(async (req: NextRequest, params: GetParams) => {
  console.log(params);
  return NextResponse.json({});
});

Additional context

No response

nextjs-auth0 version

3.5.0

Next.js version

14.2.5

Node.js version

22.4.1

The same problems exists for Pages. I created a fix for pages in #1764 , should be easy to extend this to api routes.

However, I'm not sure this is an issue that should be fixed in code. You should be validating user input anyway, so i settled on an approach like this:

eg. using zod

export default withPageAuthRequired(async function OrderPage({
  searchParams: unsafeSearchParams,
  params: unsafeParams,
}) {
  const { timerange } = z
    .object({ timerange: timerangeSchema })
    .parse(unsafeParams);
  const sParams = orderSearchParamsSchema.parse(unsafeSearchParams);

  [...]

}

The problem remains that the situation right now is far from ideal: People using Typescript will follow the docs and encounter errors.

auth0 / nextjs-auth0