PageProps Type Errors in Next.js #142577

Universe0809 · 2024-10-25T08:53:02Z

Universe0809
Oct 25, 2024

Select Topic Area

Bug

Body

Hello everyone,
I am working on a project using Next.js 15 and have defined my page as follows:
export default async function Page({ params }: { params: { slug: string[] } }) { ... }

However, during the build process, I encounter the following TypeScript error:
Type error: Type '{ params: { slug: string[]; }; }' does not satisfy the constraint 'PageProps'. Types of property 'params' are incompatible. Type '{ slug: string[]; }' is missing the following properties from type 'Promise<any>': then, catch, finally, [Symbol.toStringTag]

Could you advise on how to correctly resolve these type issues or effectively suppress this error? I've attempted to use the comment // @ts-expect-error: params type does not match expected PageProps, but the error persists.

Thank you for your assistance!

Answered by night-fury-3

Oct 25, 2024

Hi @Universe0809,
It appears that there are breaking changes in Next.js version 15 related to properties such as params. The official documentation highlights this issue (see: Next.js v15 Upgrade Guide).

To address these changes, you have a couple of options:

Downgrade: Consider reverting to an earlier version of Next.js where these breaking changes do not apply.
Update your Code: You can handle the params by awaiting them in your function as follows:
`type Params = Promise<{ slug: string[] }>;

export default async function Page({ params }: { params: Params }) {
const { slug } = await params;
}`

This approach ensures that your application remains compatible with the latest version of Ne…

View full answer

iliya06 · 2024-10-25T08:53:24Z

github-actions[bot]
bot Oct 25, 2024

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

Your input will be carefully reviewed and cataloged by members of our product teams.
- Due to the high volume of submissions, we may not always be able to provide individual responses.
- Rest assured, your feedback will help chart our course for product improvements.
Other users may engage with your post, sharing their own perspectives or experiences.
GitHub staff may reach out for further clarification or insight.
- We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

Upvote and comment on other user feedback Discussions that resonate with you.
Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

1 reply

iliya06 Nov 25, 2024

For assistance, contact Roadrunner Email Support on <+ 1 - 8 8 8 - 8 4 8- 2 4 0 9 ⭐(Toll-Free).

Call Roadrunner Email Support at <+ 1 - 8 8 8 - 8 4 8- 2 4 0 9 ⭐ (Toll-Free) ☎️ to speak with skilled support representatives.
If you’ve changed or forgotten your password, you can typically recover access by clicking the “Forgot Password” link on the login page. This process usually involves verification through an alternate email address or phone number associated with your account or answering security questions.

night-fury-3 · 2024-10-25T15:25:57Z

night-fury-3
Oct 25, 2024

Hi @Universe0809,
It appears that there are breaking changes in Next.js version 15 related to properties such as params. The official documentation highlights this issue (see: Next.js v15 Upgrade Guide).

To address these changes, you have a couple of options:

Downgrade: Consider reverting to an earlier version of Next.js where these breaking changes do not apply.
Update your Code: You can handle the params by awaiting them in your function as follows:
`type Params = Promise<{ slug: string[] }>;

export default async function Page({ params }: { params: Params }) {
const { slug } = await params;
}`

This approach ensures that your application remains compatible with the latest version of Next.js.

Thank you for taking my suggestion into account.
Please feel free to contact me if you have any questions.

6 replies

Universe0809 Oct 25, 2024
Author

It works now.
Thank you so much.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

PageProps Type Errors in Next.js #142577

{{title}}

Replies: 2 comments 7 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

PageProps Type Errors in Next.js #142577

Select Topic Area

Body

Replies: 2 comments · 7 replies

github-actions[bot] bot Oct 25, 2024

Universe0809 Oct 25, 2024 Author

Replies: 2 comments 7 replies

github-actions[bot]
bot Oct 25, 2024

Universe0809 Oct 25, 2024
Author