feat(nextjs): Add support for Next.js 13 app router

[mayank1513]

• fixes Next.js 13 app router + @sentry/wizard breaks typing #307 and Wizard doesn't work with Next.js app dir because it tries to place file in pages folder #241
• checks for appRouter as well
• defaults to creating a pages folder if neither page nor app router is detected

[mayank1513]

Also fixes #241

[lforst]

Hey, thanks for this PR. We are very likely gonna merge it but I will hold off for a bit because I am planning on adding API routes support very soon and then we can drop the special casing.

[mayank1513]

Hey, thanks for this PR. We are very likely gonna merge it but I will hold off for a bit because I am planning on adding API routes support very soon and then we can drop the special casing.

Thanks.

Can I help in adding support for route handlers?

[lforst]

Hey, thanks for this PR. We are very likely gonna merge it but I will hold off for a bit because I am planning on adding API routes support very soon and then we can drop the special casing.

Thanks.

Can I help in adding support for route handlers?

Yes of course. PRs are always welcome!

[andycansdale]

Just to add to this, I spent a number of hours trying to debug why my middleware suddenly stopped working when installing Sentry using the wizard. I eventually tracked it down to the addition of a pages folder on my root. As I am using a src/ directory for my app folder, middleware, etc. this caused the middleware to not be run.

A possible solution might be add a step that asks the user if they are using a src folder, or perhaps check the location of the existing app directory. Not sure if it's relevant, but my app did not have a pages directory before it was added by Sentry since we are using the app router for everything.

[mayank1513]

Just to add to this, I spent a number of hours trying to debug why my middleware suddenly stopped working when installing Sentry using the wizard. I eventually tracked it down to the addition of a pages folder on my root. As I am using a src/ directory for my app folder, middleware, etc. this caused the middleware to not be run.

A possible solution might be add a step that asks the user if they are using a src folder, or perhaps check the location of the existing app directory. Not sure if it's relevant, but my app did not have a pages directory before it was added by Sentry since we are using the app router for everything.

This is taken care of in this PR.

[github-actions]

This pull request 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]

Hi, I think we have waited enough for updates to sentry core functionality -> out of box support for app directory route handlers. I think we shouldn't block this PR for that. This would be against agile principles.

[lforst]

@mayank1513 We will still go with the plan and merge this when route handlers are working.

Last week most of Sentry was in a hackathon and we didn't operate as usual so things should speed up again now.