Command
npm run lintExplanation
The Next.js ESLint integration runs static code analysis across your project, helping you catch syntax errors, unused variables, and unsafe patterns. It supports automatic fixing and works with custom configurations via `.eslintrc.json` or `next.config.js`. Linting helps maintain readability and prevents bugs early in development.
Common Use Cases
- •Check code style and consistency
- •Catch syntax and logic errors before build
- •Integrate ESLint with CI/CD pipelines
Best Practices
- ✓Run linting before committing changes
- ✓Use `.eslintignore` to skip generated or build files
- ✓Combine with Prettier for consistent formatting
Common Mistakes to Avoid
- ⚠Ignoring lint warnings instead of fixing root causes
- ⚠Using incompatible ESLint plugin versions
Troubleshooting
Problem: Linting fails after update
Solution: Ensure ESLint version matches Next.js supported range.
Problem: Too many lint errors
Solution: Use `--fix` to auto-correct format issues.
Examples
Run ESLint on the project
npm run lintRun linting using Yarn
yarn lint