Error occurred prerendering page "/note/cli-환경에서-여러-명령어를-동시에-실행하기". Error: Cannot find module './note/cli-%ED%99%98%EA%B2%BD%EC%97%90%EC%84%9C-%EC%97%AC%EB%9F%AC-%EB%AA%85%EB%A0%B9%EC%96%B4%EB%A5%BC-%EB%8F%99%EC%8B%9C%EC%97%90-%EC%8B%A4%ED%96%89%ED%95%98%EA%B8%B0/index.mdx'

TL;DR

Decode URL-encoded slugs in generateStaticParams() to match Next.js's dynamic route resolution.

Guidance

• Verify that generateStaticParams() returns URL-encoded slugs by logging the output and comparing it to the expected raw slug.
• Use decodeURIComponent(slug) to decode the URL-encoded slug inside generateStaticParams() to ensure consistency with Next.js's dynamic route resolution.
• Test the dev server and build with the updated generateStaticParams() to confirm that the "missing param" error and MODULE_NOT_FOUND issue are resolved.
• Consider adding a check to ensure that the decoded slug matches the expected raw slug to prevent potential issues with non-ASCII characters.

Example

// In generateStaticParams()
const decodedSlug = decodeURIComponent(slug);
// Use decodedSlug for further processing

Notes

The provided workaround of calling decodeURIComponent(slug) inside the page component resolves the module loading issue, but the dev server still logs the "missing param" error. Decoding the slug in generateStaticParams() should resolve both issues.

Recommendation

Apply the workaround by decoding the URL-encoded slug in generateStaticParams() to ensure consistency with Next.js's dynamic route resolution. This should resolve the "missing param" error and MODULE_NOT_FOUND issue.