mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-16 23:41:43 +00:00
2b2ae4ca49
Some checks failed
LiteLLM Rust / rustfmt, clippy, test (push) Has been cancelled
* refactor(ui): migrate MCP, callback, guardrail, SSO, and search tool logos to the shared Logo component Third step of the logo consolidation. Every remaining rogue logo pattern now renders through Logo: MCP well-known grid and backend mcp_info.logo_url sites (which previously skipped resolveLogoSrc and broke under non-root mounts), callback maps in callback_info_helpers plus the backend-provided variant in settings.tsx, the guardrail map with the garden dataset now deriving logos from guardrailLogoMap instead of duplicating them, the SSO map deduped from two verbatim copies into SSOSettings/constants.ts, search tools' filename guessing replaced with an explicit static-import map, and the two straggler sites in EntityUsage and model_info_view. Static-map path strings become bundled static imports throughout; backend-provided URLs stay runtime strings resolved via Logo src mode. MCPLogoSelector still stores stable /ui/assets/logos paths so existing DB rows keep matching. okta's logo remains an external hotlink pending a vendored local asset. promptguard.svg drops a mismatched intrinsic dimension attribute for the Turbopack import parser. * fix(ui): make resolveLogoSrc idempotent for values already carrying the server root path Stored mcp_info.logo_url values from sub-path deployments could bake in the deployment root because the old bare img sites did no resolution. Prefixing those again produced /litellm/litellm/... and a fallback avatar. Skip prefixing when the value already starts with the current normalized root segment; paths whose first segment merely begins with the root text still get prefixed. |
||
|---|---|---|
| .. | ||
| e2e_tests | ||
| 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.