chore(components): rename legacy-ui/ to site/ and drop @/UI alias#104
Merged
ahnafnafee merged 1 commit intomainfrom Apr 26, 2026
Merged
chore(components): rename legacy-ui/ to site/ and drop @/UI alias#104ahnafnafee merged 1 commit intomainfrom
ahnafnafee merged 1 commit intomainfrom
Conversation
The folder previously called legacy-ui/ wasn't legacy — it holds active bespoke composition components (Header, Footer, Nav, AppLayoutPage, Hero, Searchbar, BackToTop, EmptyResult, MobileNav, ThemeMenu, link wrappers, image wrappers) that compose shadcn primitives plus project-specific state. The legacy- prefix was a transitional concession during the shadcn migration to dodge the Windows case-collision with ui/. Rename to site/ now that the migration is settled. Mechanical changes: - git mv src/components/legacy-ui → src/components/site - sed sweep: @/UI/ → @/components/site/, @/components/legacy-ui/ → @/components/site/ (~38 files) - tsconfig.json: drop @/UI and @/UI/* path aliases (no longer needed) - .prettierrc.js: drop the @/UI group from importOrder - CLAUDE.md: update Path Aliases + Component Layout sections to describe ui/ + site/ instead of legacy-ui/ Verified locally: yarn type-check, yarn lint, yarn test (48/48), yarn build (50 routes) — all clean.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The folder previously called
legacy-ui/wasn't legacy — it holds active bespoke composition components (Header, Footer, Nav, AppLayoutPage, Hero, Searchbar, BackToTop, EmptyResult, MobileNav, ThemeMenu, link wrappers, image wrappers) that compose shadcn primitives plus project-specific state. Thelegacy-prefix was a transitional concession during the shadcn migration to dodge the Windows case-collision withui/. Rename tosite/now that the migration is settled.What changed
git mv src/components/legacy-ui → src/components/site@/UI/→@/components/site/,@/components/legacy-ui/→@/components/site/(~38 files touched)tsconfig.json: drop@/UIand@/UI/*path aliases (no longer needed).prettierrc.js: drop the@/UIgroup fromimportOrderCLAUDE.md: update Path Aliases + Component Layout sections to describeui/+site/instead oflegacy-ui/Mental model after this PR
src/components/ui/— shadcn primitives, generated/synced vianpx shadcn@latest add. Don't hand-edit.src/components/site/— bespoke composition components specific to this site. Composeui/+ project hooks/state.Test plan
yarn type-check— cleanyarn lint— cleanyarn test— 48/48 passyarn build— 50 routes generatedyarn dev— header, footer, nav, mobile menu, theme toggle, dialogs all still renderSingle commit so it's easy to revert if anything misfires.