Add component library initialization option to create-next-app

[Sudhanshu062]

Goals

1. Allow developers to choose a UI/component library (e.g., shadcn, tremor, or none) during the create-next-app setup.
2. Simplify initial project setup by optionally preconfiguring a chosen component library.
3. Reduce repetitive manual installation and configuration of common UI libraries.

Non-Goals

1. Supporting all available component libraries in the ecosystem. (maybe later)
2. Enforcing opinionated design or layout choices from the selected libraries.
3. Maintaining full feature parity or long-term support for third-party UI libraries within the Next.js core.

Background

When starting a new project with create-next-app, developers often follow up with manual setup steps to add a UI/component library. Libraries like shadcn/ui and tremor are increasingly popular in the Next.js community, and scaffolding support could significantly streamline the initial developer experience.

Proposal

Introduce an additional prompt during the create-next-app initialization flow:

Would you like to initialize the project with a component library?

Options: shadcn, tremor, none

Based on the selection, the CLI would:

• Install required packages (e.g., shadcn/ui or @tremor/react)
• Optionally run basic setup commands (e.g., npx shadcn-ui@latest init)
• Optionally scaffold related configuration files

This would be an opt-in feature, preserving the zero-config behavior for users who select "none."

Are you interested in contributing?

Yes, I would be interested in contributing to this feature.