Skip to content

[area:shadcn] daisyUI → shadcn/ui 전환 #8

Description

@fray-cloud

Scope

  • remove daisyui from package.json and Tailwind config
  • initialize shadcn/ui (latest, App Router compatible)
  • replace daisyUI usage across new-component/ and new-site/
  • audit @mui/joy and @mui/x-date-pickers; replace where shadcn covers it

Acceptance

  • npx nx affected -t lint test build green
  • No daisyUI classes or imports remain (git grep clean)
  • No commit leaves the repo in a mixed daisyUI + shadcn state
  • MUI kept only where shadcn has no replacement (documented)

Depends on

Research

Findings recorded in issue comment.

Risk

med — visual regressions across every page; coherent landing requires planning per-component swaps.

Steps

  1. Init shadcn in the Next app post-migration.
  2. Inventory daisyUI usage; group by component.
  3. Swap components in coherent batches (one feature area per PR).
  4. Remove daisyui dependency only after the last usage is gone.
  5. MUI audit pass.

Sub-tasks

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Priority 1 - higharea:shadcnRoadmap area: Tailwind/shadcn migration

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions