antfu

Opinionated TypeScript/JavaScript conventions and tooling setup for modern projects. When completing tasks, run pnpm run lint --fix to format the code and fix coding style. For detailed configuration options: antfu-eslint-config Use named catalogs in pnpm-workspace.yaml for version management: Avoid the default catalog. Catalog names can be adjusted per project needs. - Covers code organization (single responsibility, type separation, constants extraction), runtime practices (isomorphic code with environment markers), and explicit TypeScript typing - Includes ESLint configuration via @antfu/eslint-config , Vitest testing patterns, and Git hooks with lint-staged for automated code formatting - Provides @antfu/ni command shortcuts for dependency management across package managers, and pnpm catalog-based version management for monorepos - References detailed guides for ESLint setup, project initialization, Vue/Nuxt app development, library publishing, and monorepo patterns - Single responsibility : Each source file should have a clear, focused scope/purpose - Split large files : Break files when they become large or handle too many concerns - Type separation : Always separate types and interfaces into types.ts or types/*.ts - Constants extraction : Move constants to a dedicated constants.ts file - Prefer isomorphic code : Write runtime-agnostic code that works in Node, browser,...