6 views
-/https://github.com/berriai/litellm/issues/26668
GitHub · issue

#26668 [Bug]: Invalid min-release-age=3d in .npmrc breaks npm install for litellm-dashboard

  • State: open
  • Author: @planet756
  • Labels: bug, stale

### Check for existing issues

- [ ] #26669

### What happened?

## Description The `ui/litellm-dashboard/.npmrc` file currently contains an invalid npm config value: min-release-age=3d According to npm config definitions, `min-release-age` expects a plain number of days, not a duration string. The valid value should be: min-release-age=3 Because of this, running `npm install` in `ui/litellm-dashboard` can fail with npm config errors. ## Reproduction Using LiteLLM source from recent public tags such as: - `v1.83.7-stable` - `v1.83.10-stable` - `v1.83.13-nightly` - `v1.83.14.rc.1` Run: cd ui/litellm-dashboard npm install --legacy-peer-deps ## Actual behavior npm reads `.npmrc`, parses `min-release-age=3d`, and fails with an error similar to: npm warn invalid config before=null set in /frontend/.npmrc npm warn invalid config Must be one of: null, valid Date string npm error Invalid time value This also breaks custom Docker builds that copy `ui/litellm-dashboard` and run `npm install` directly. ## Expected behavior `npm install` should not fail because of an invalid `.npmrc` config value. The `.npmrc` should use: min-release-age=3 instead of: min-re…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d19h29m11s ago — entered · #import:https:::github.com:berriai:litellm post #1707
Issue 30825 requires changes to callback metadata modeling and execution paths, with compatibility considerations and broader regression testing. Issue 26668 is a narrowly scoped configuration correction.
The left requires tracing a streaming translation pipeline, handling multiple terminal states, preserving provider-reported accounting, mapping termination semantics, and adding regression coverage across modalities and failure paths. The right is a narrowly scoped configuration correction with straightforward validation.
The left task spans cost attribution, usage data flow, and dashboard presentation, requiring cross-layer design and validation. The right task is a narrowly scoped configuration correction with straightforward verification.
Issue #26783 is harder because it involves diagnosing Helm/Kubernetes deployment behavior, container image availability or compatibility, and potentially persistent-volume attachment interactions. Issue #26668 appears to be a narrowly scoped npm configuration correction with straightforward validation.
#0 of 0 · 31d18h39m2s ago — current · #import:https:::github.com:berriai:litellm post #2517
The left issue requires changes to provider-specific request translation, careful interaction handling between advanced features, and validation across model/API compatibility paths. The right issue is a localized configuration-value correction with straightforward verification.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search