validate-config

To detect deprecated Next.js config options, validate next.config.js/ts/mjs files against your current Next.js version. This process flags risky settings and prints each finding with recommended fixes to reduce upgrade friction and runtime issues.

Next.js config validation checks for deprecated options, misconfigurations, and risky settings across images, headers, redirects, and env misuse. It reads package.json context to flag issues and suggest safe defaults for performance and security.

Yes, you can lint next.config.js, next.config.ts, and next.config.mjs files. The validation process analyzes these configuration formats to identify deprecated options and applies checks across different Next.js project versions.

You can automate finding misconfigurations by running a validation skill that scans your Next.js configuration files. It automatically identifies deprecated options and provides remediation steps by analyzing common configuration sections.

Package.json context is optional but recommended to validate Next.js config issues accurately. It allows the validation process to read your current Next.js version and precisely flag deprecated options based on that specific version.