@acarmisc/backstage-plugin-litellm 0.30.0 → 0.31.0

package/dist/components/LiteLLMBudgetGauges.d.ts

@@ -1,19 +1,31 @@
 /**
- * Condensed budget card for a homepage column: one ring gauge per
- * enforcement level (key → personal → team) plus a month-to-date daily
- * token-usage mini-chart, in a fixed four-column row. Each gauge shows the
- * limit nearest its cap; where the full `LiteLLMBudgetWidget` lists every
- * limit as a spend-vs-cap meter, this trades detail for density — a single
- * row with a label and spend figure under each gauge, and the MTD token
- * total under the chart.
+ * Condensed budget card for a homepage column: spend KPIs on one line,
+ * one inline row per enforcement level (key → personal → team), and a
+ * month-to-date daily spend strip, in a fixed card that never reflows.
  *
- * Gauges are always rendered in the same order, with an empty ring when the
- * user has no cap at that level, so the card keeps a stable shape as data
- * loads and across users. When a level holds several limits, the ring shows
- * the one closest to its cap and a "+N more" link counts the rest.
+ * The card is deliberately *row*-shaped rather than four side-by-side
+ * columns: a four-column grid lets one long key alias widen its track (a
+ * `1fr` track is only as narrow as its widest unbreakable content) and lets
+ * each column wrap its own number of caption lines, so the text under the
+ * rings drifts out of alignment. Rows share three fixed tracks — ring,
+ * flexible name, right-aligned amount — so every figure is in the same
+ * place and tabular numerals line up, and a long name ellipsizes inside
+ * `minmax(0, 1fr)` instead of stretching anything.
  *
- * The usage period is frozen to month-to-date (no period selector): the
- * chart always covers the 1st of the current month through today.
+ * Each row shows the limit nearest its cap at that level: the ring carries
+ * the percentage, the middle track the level tag, limit name and a short
+ * note (over cap, a `+N more` link, or the key id / email), and the right
+ * track the spend-vs-cap dollars over the reset window — one caption per
+ * fact, so the reset window is never printed twice in a row. Where the full `LiteLLMBudgetWidget` lists every limit as a
+ * meter card, this trades detail for density. Gauges are always rendered in
+ * the same order, with an empty ring when the user has no cap at that
+ * level, so the card keeps a stable shape as data loads and across users.
+ *
+ * Above the rows sit two inline KPIs — **today spent** (with a
+ * day-over-day hint) and month-to-date spend — both derived from the same
+ * month-to-date usage call, so the indicator costs no extra request. The
+ * usage period is frozen to month-to-date (no period selector): the chart
+ * always covers the 1st of the current month through today.
  *
  * The bottom action bar is composable: pass any subset of `ctas` — generate
  * a new key, open the LiteLLM module, or expand the full per-limit list in
@@ -34,7 +46,7 @@ export interface LiteLLMBudgetGaugesProps {
      * home page grid) that already provide a titled card. Defaults to false.
      */
     bare?: boolean;
-    /** Ring diameter in px. Defaults to 72. */
+    /** Ring diameter in px. Defaults to 56. */
     size?: number;
     /** Where the "+N more" key link points. Defaults to the Keys tab. */
     keysHref?: string;

package/dist/homeWidgetHelpers.d.ts

@@ -19,6 +19,19 @@ export declare function sparklineAriaLabel(points: Array<{
     date: string;
     spend: number;
 }>): string;
+/**
+ * Spend recorded on the local calendar day `now` (defaults to today) in a
+ * daily-spend series. Days the API omits count as zero — no spend recorded
+ * yet — so a chart that simply hasn't seen a request today still answers
+ * `$0.00` instead of `undefined`.
+ *
+ * `now` is overridable so the same helper yields yesterday's figure
+ * (`spendOnDay(points, yesterday)`) for a day-over-day hint.
+ */
+export declare function spendOnDay(points: Array<{
+    date: string;
+    spend: number;
+}>, now?: Date): number;
 /**
  * Format usage metrics as a single summary line: '$X spent · YM in · ZM out'
  * Handles zero usage and undefined values gracefully.