Fixes the missing Next.js export names reported in the issue by adding support for three additional Next.js App Router API functions to the allowExportNames configuration in the Next.js config preset.

Changes

Added the following export names to the Next.js config's allowExportNames array:

• generateImageMetadata - Next.js function for generating image metadata in page/layout files
• generateSitemaps - Next.js function for generating sitemaps
• generateStaticParams - Next.js function for generating static route parameters

These functions are part of Next.js's App Router API and can be exported alongside React components in page/layout files without triggering fast refresh issues.

Example Usage

With this change, the following code will no longer trigger an ESLint warning when using the Next.js config:

// app/blog/[slug]/page.tsx
export async function generateStaticParams() {
  const posts = await fetch('https://...').then(res => res.json())
  return posts.map((post) => ({ slug: post.slug }))
}

export default function Page({ params }: { params: { slug: string } }) {
  return <div>Blog post: {params.slug}</div>
}

Testing

• All existing tests pass (69 tests)
• Linting and build complete successfully

Fixes #91

Fixes #91

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.