Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: Invalid min-release-age=3d in .npmrc breaks npm install for litellm-dashboard [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26668•Fetched 2026-04-29 06:13:00
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
planet756planet756
Participants
planet756planet756
Timeline (top)
labeled ×1

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.

Error Message

npm warn invalid config before=null set in /frontend/.npmrc npm warn invalid config Must be one of: null, valid Date string npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-23T08_06_41_945Z-debug-0.log ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux && rm -f package-lock.json && npm install --legacy-peer-deps && npm run build && mkdir -p /var/lib/litellm/ui /var/lib/litellm/assets && cp -r ./out/* /var/lib/litellm/ui/" did not complete successfully: exit code: 1

Root Cause

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-release-age=3d

Current workaround

The official Dockerfile appears to work around this by temporarily moving .npmrc before running npm install/ci. For custom Docker builds, the workaround is to remove or patch .npmrc before running npm install: RUN sed -i 's/min-release-age=3d/min-release-age=3/' .npmrc or: RUN rm -f .npmrc

Additional context

It looks like this was already fixed once in PR #25058, which changed min-release-age=3d to min-release-age=3, but that fix appears to have landed only in the litellm_oss_staging_04_06_2026 branch and has not been propagated to main or recent public release tags. Recent checked refs still contain min-release-age=3d in ui/litellm-dashboard/.npmrc:

  • v1.83.7-stable
  • v1.83.10-stable
  • v1.83.13-nightly
  • v1.83.14.rc.1
  • main
  • litellm_internal_staging Could this fix be applied to main / the current release branch?

Fix Action

Fix / Workaround

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-release-age=3d

Current workaround

The official Dockerfile appears to work around this by temporarily moving .npmrc before running npm install/ci. For custom Docker builds, the workaround is to remove or patch .npmrc before running npm install: RUN sed -i 's/min-release-age=3d/min-release-age=3/' .npmrc or: RUN rm -f .npmrc

Additional context

It looks like this was already fixed once in PR #25058, which changed min-release-age=3d to min-release-age=3, but that fix appears to have landed only in the litellm_oss_staging_04_06_2026 branch and has not been propagated to main or recent public release tags. Recent checked refs still contain min-release-age=3d in ui/litellm-dashboard/.npmrc:

  • v1.83.7-stable
  • v1.83.10-stable
  • v1.83.13-nightly
  • v1.83.14.rc.1
  • main
  • litellm_internal_staging Could this fix be applied to main / the current release branch?

Code Example

npm warn invalid config before=null set in /frontend/.npmrc
npm warn invalid config Must be one of: null, valid Date string
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-23T08_06_41_945Z-debug-0.log
ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux     && rm -f package-lock.json     && npm install --legacy-peer-deps     && npm run build     && mkdir -p /var/lib/litellm/ui /var/lib/litellm/assets    && cp -r ./out/* /var/lib/litellm/ui/" did not complete successfully: exit code: 1
RAW_BUFFERClick to expand / collapse

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-release-age=3d

Current workaround

The official Dockerfile appears to work around this by temporarily moving .npmrc before running npm install/ci. For custom Docker builds, the workaround is to remove or patch .npmrc before running npm install: RUN sed -i 's/min-release-age=3d/min-release-age=3/' .npmrc or: RUN rm -f .npmrc

Additional context

It looks like this was already fixed once in PR #25058, which changed min-release-age=3d to min-release-age=3, but that fix appears to have landed only in the litellm_oss_staging_04_06_2026 branch and has not been propagated to main or recent public release tags. Recent checked refs still contain min-release-age=3d in ui/litellm-dashboard/.npmrc:

  • v1.83.7-stable
  • v1.83.10-stable
  • v1.83.13-nightly
  • v1.83.14.rc.1
  • main
  • litellm_internal_staging Could this fix be applied to main / the current release branch?

Steps to Reproduce

  1. Use a LiteLLM source release that still contains min-release-age=3d in ui/litellm-dashboard/.npmrc, for example v1.83.7-stable.
  2. Enter the dashboard directory: cd ui/litellm-dashboard
  3. Run npm install: npm install --legacy-peer-deps
  4. Alternatively, build a custom Docker image that copies ui/litellm-dashboard and runs npm install --legacy-peer-deps before building the frontend.

Relevant log output

npm warn invalid config before=null set in /frontend/.npmrc
npm warn invalid config Must be one of: null, valid Date string
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-23T08_06_41_945Z-debug-0.log
ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux     && rm -f package-lock.json     && npm install --legacy-peer-deps     && npm run build     && mkdir -p /var/lib/litellm/ui /var/lib/litellm/assets    && cp -r ./out/* /var/lib/litellm/ui/" did not complete successfully: exit code: 1

What part of LiteLLM is this about?

Other

What LiteLLM version are you on ?

v1.83.7-stable

Twitter / LinkedIn details

No response

extent analysis

TL;DR

Update the min-release-age value in ui/litellm-dashboard/.npmrc to a plain number, such as min-release-age=3, to resolve the npm config error.

Guidance

  • Verify the current value of min-release-age in ui/litellm-dashboard/.npmrc to confirm it is set to 3d.
  • Update the min-release-age value to a plain number, such as min-release-age=3, to match the expected format.
  • Run npm install --legacy-peer-deps again to test if the update resolves the error.
  • For custom Docker builds, apply the workaround by running sed -i 's/min-release-age=3d/min-release-age=3/' .npmrc or rm -f .npmrc before running npm install.

Example

# Update min-release-age value
sed -i 's/min-release-age=3d/min-release-age=3/' ui/litellm-dashboard/.npmrc

# Run npm install
npm install --legacy-peer-deps

Notes

The fix was previously applied in PR #25058 but has not been propagated to the main branch or recent public release tags. This update should be applied to the current release branch to resolve the issue.

Recommendation

Apply the workaround by updating the min-release-age value to a plain number, such as min-release-age=3, to resolve the npm config error. This fix should be applied to the main branch and recent public release tags to prevent future occurrences.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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-release-age=3d

#GPU setup#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: Invalid min-release-age=3d in .npmrc breaks npm install for litellm-dashboard [1 participants]