Next.js 13 app router + @sentry/wizard breaks typing

[trbarton]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

7.56.0

Framework Version

13.4.5

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

This bug appears in a Next 13 app router project using typescript and the App router exclusively.

Create a project and set up a dynamic route in the app directory. e.g. app/post/[id]/page.tsx
On the new page use the useParams() hook from next/navigation to get the id
const { id } = useParams();
This currently will be typed as a string. Running the build command should also be successful

Now run the sentry wizard as per the Sentry next.js setup instructions:
npx @sentry/wizard@latest -i nextjs

Now building will fail due to a type error. This is due to the wizard creating a test route in the pages directory.
We now have both a pages and app directory so next/navigation uses the "compat" types. id is no longer of type string
but instead is of type: Record<string, string, string[]> | null

This caveat should probably be documented in the Next.js setup instructions

Expected Result

An app router project to build successfully after running the sentry wizard

Actual Result

[lforst]

Out of curiosity, will removing the test page fix this error again?

I think we should add a test page to the app dir instead, if the router is used.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[mayank1513]

I have created PR fixing this issue - #385