[feat]: Add linter choice (ESLint/Biome) option during initialization

[marcelbaklouti]

Feature description

Feature Request

I'd like to suggest adding an option during the initialization process (npx shadcn@latest init, pnpm dlx shadcn@latest init, or bunx shadcn@latest init) that allows users to choose between ESLint or Biome for their project's linting configuration.

Current Behavior

Currently, when initializing a new project with shadcn, the CLI doesn't provide an option to choose between different linting tools. It appears to default to ESLint configuration.

Desired Behavior

During initialization, after other configuration options (like styling, typescript, etc.), I'd like to see a prompt similar to:

Which linter would you like to use?
> ESLint
Biome

This would then set up the appropriate configuration files based on the user's choice:

• If ESLint: Add .eslintrc.json and .eslintignore
• If Biome: Add biome.json configuration

Why This Matters

Biome is gaining popularity as a fast, modern alternative to ESLint, especially in projects using React/Next.js. Giving users this choice during setup would:

1. Increase flexibility for developers with different preferences
2. Support modern tooling options
3. Align with the project's philosophy of customization and developer choice

I'd be happy to help with implementation if this feature is considered!

Affected component/components

No response

Additional Context

Biome (https://biomejs.dev/) is positioned as a fast alternative to ESLint, and many developers are adopting it in their workflows, especially for React/Next.js projects.

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues and PRs