mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-11 03:38:38 +00:00
6147b3ce6e
* refactor(ui): install the shadcn field primitive `components/shared/form/field.tsx` was the upstream base-vega `field` source living outside `components/ui/`. It exported the same ten symbols as upstream, so `npx shadcn add` could never update it and it had already drifted: its `FieldLabel` was missing the hover and focus-visible ring utilities upstream now ships for labels that wrap a nested field. Install the primitive and point the 77 importers at it. The copy is deleted rather than kept as a wrapper because it added nothing beyond `forwardRef`, which React 19 makes unnecessary since `ref` arrives as an ordinary prop. `field.test.tsx` moves next to the primitive with no edits to its contents, and its nineteen tests, ref assertions included, pass against the generated file. That is the evidence the swap is behaviour-preserving. Two nested-field call sites pick up the upstream hover and focus-visible styling that the stale copy had been missing. (cherry picked from commit 947f7fa674c83bfc57f43ad8bfc89c894da947a2) * test(ui): cover the nested-field interaction cues FieldLabel had lost The stale copy of `field` was missing the hover, focus-visible and disabled selectors upstream applies to a label that wraps a nested field, so installing the primitive restored them with nothing asserting they stay. Assert the class contract rather than the rendered effect. jsdom evaluates neither `:has()` nor `:focus-visible`, and Tailwind is not compiled under vitest, so a test that clicked or tabbed would pass on an element with no styling at all. Checking the utilities are present is the assertion that actually fails when they go missing, which is the way they were lost before. Verified by stripping the four selectors from the primitive: both tests fail, and both pass once it is restored. (cherry picked from commit 5a5dbf64270d9d1285dbc4a7af76bb3d927778a8) |
||
|---|---|---|
| .. | ||
| public | ||
| scripts | ||
| src | ||
| tests | ||
| .env.development | ||
| .env.production | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| build_release_ui.sh | ||
| build_ui.sh | ||
| build_ui_custom_path.sh | ||
| CLAUDE.md | ||
| components.json | ||
| eslint-budgets.json | ||
| eslint-suppressions.json | ||
| eslint.config.mjs | ||
| knip.json | ||
| next.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.tsbuildinfo | ||
| vitest.config.ts | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.