typescript-conventions

Enforce strict TypeScript conventions by applying rules that prohibit 'any' types, require explicit props interfaces, and mandate server components by default. This approach ensures codebase consistency during component creation and refactoring.

Standardize React component props typing by requiring explicit interfaces and utilizing 'as const' assertions. This method integrates with linting tools to provide actionable feedback on file modifications.

Yes, the convention checker supports Tailwind CSS by enforcing specific Tailwind usage patterns within React components. It analyzes .tsx files to ensure styling conventions are maintained during UI updates.

Fix 'no any' violations during a TypeScript refactor by defining explicit interfaces and type exports for your variables. The convention checks highlight these violations and guide you toward strict type definitions.

Specify server vs client component rules in Next.js App Router whenever creating or modifying components. Enforcing server components by default ensures proper async handling and state management conventions are applied.

These linting rules are specifically designed for Next.js App Router projects, covering patterns like server components and specific Tailwind usage. Applying them to general React apps outside Next.js may not yield appropriate convention feedback.