Issue Station
Sign In
Tools hereToolbox

litellm - ✅(Solved) Fix [Bug]: Invalid min-release-age config in .npmrc file breaks npm install [1 pull requests, 1 comments, 2 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#25057•Fetched 2026-04-08 02:34:56
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
KontinuationKontinuation
Participants
KontinuationKontinuationnightcitybladenightcityblade
Timeline (top)
cross-referenced ×2commented ×1labeled ×1referenced ×1

Error Message

npm warn invalid config before=null set in /home/kontinuation/workspace/github/BerriAI/litellm/ui/litellm-dashboard/.npmrc npm warn invalid config Must be one of: null, valid Date string npm error Invalid time value npm error A complete log of this run can be found in: /home/kontinuation/.npm/_logs/2026-04-03T05_48_29_660Z-debug-0.log npm warn invalid config before=null set in /home/kontinuation/workspace/github/BerriAI/litellm/ui/litellm-dashboard/.npmrc npm warn invalid config Must be one of: null, valid Date string npm error Invalid time value npm error A complete log of this run can be found in: /home/kontinuation/.npm/_logs/2026-04-03T05_48_29_660Z-debug-0.log

Fix Action

Fixed

PR fix notes

PR #25058: fix: use numeric npm min-release-age config

Description (problem / solution / changelog)

Relevant issues

Fixes #25057

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • [N/A] I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • [N/A] My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.

  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Type

🐛 Bug Fix

Changes

  • replace invalid min-release-age=3d with min-release-age=3 in all six .npmrc files added by #24838
  • preserve the intended 3-day npm supply-chain hardening behavior using the config format npm actually accepts
  • fix npm install failures in project directories such as ui/litellm-dashboard

Validation

  • reproduced the failure locally with npm install in ui/litellm-dashboard
  • verified npm install succeeds after the .npmrc fix

Changed files

  • .npmrc (modified, +1/-1)
  • litellm-js/proxy/.npmrc (modified, +1/-1)
  • litellm-js/spend-logs/.npmrc (modified, +1/-1)
  • tests/proxy_admin_ui_tests/.npmrc (modified, +1/-1)
  • tests/proxy_admin_ui_tests/ui_unit_tests/.npmrc (modified, +1/-1)
  • ui/litellm-dashboard/.npmrc (modified, +1/-1)

Code Example

# Protects local npm install only — npm ci (used in CI) ignores this
min-release-age=3d

---

min-release-age=3

---

$ npm install
npm warn invalid config before=null set in /home/kontinuation/workspace/github/BerriAI/litellm/ui/litellm-dashboard/.npmrc
npm warn invalid config Must be one of: null, valid Date string
npm error Invalid time value
npm error A complete log of this run can be found in: /home/kontinuation/.npm/_logs/2026-04-03T05_48_29_660Z-debug-0.log

---

cd ui/litellm-dashboard
npm install

---

$ npm install
npm warn invalid config before=null set in /home/kontinuation/workspace/github/BerriAI/litellm/ui/litellm-dashboard/.npmrc
npm warn invalid config Must be one of: null, valid Date string
npm error Invalid time value
npm error A complete log of this run can be found in: /home/kontinuation/.npm/_logs/2026-04-03T05_48_29_660Z-debug-0.log
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

https://github.com/BerriAI/litellm/pull/24838 tried to harden the supply chain by specifying the following option:

# Protects local npm install only — npm ci (used in CI) ignores this
min-release-age=3d

However, 3d is an invalid config value for min-release-age. It expects null or Number, the correct config should be

min-release-age=3

The min release age is measured in the number of days.

The invalid config cause npm install failure in ui/litellm-dashboard directory:

$ npm install
npm warn invalid config before=null set in /home/kontinuation/workspace/github/BerriAI/litellm/ui/litellm-dashboard/.npmrc
npm warn invalid config Must be one of: null, valid Date string
npm error Invalid time value
npm error A complete log of this run can be found in: /home/kontinuation/.npm/_logs/2026-04-03T05_48_29_660Z-debug-0.log

Steps to Reproduce

cd ui/litellm-dashboard
npm install

There are multiple .npmrc files submitted, so npm installs in other places might be affected as well.

Relevant log output

$ npm install
npm warn invalid config before=null set in /home/kontinuation/workspace/github/BerriAI/litellm/ui/litellm-dashboard/.npmrc
npm warn invalid config Must be one of: null, valid Date string
npm error Invalid time value
npm error A complete log of this run can be found in: /home/kontinuation/.npm/_logs/2026-04-03T05_48_29_660Z-debug-0.log

What part of LiteLLM is this about?

Other

What LiteLLM version are you on ?

latest main

Twitter / LinkedIn details

No response

See Also

https://github.com/npm/cli/pull/8965/changes#diff-6f21b9547f08121788002c1b5494afcd450c3d6a9a6f4e1f452d71d2764515b4R1124-R1137

extent analysis

TL;DR

The most likely fix is to update the min-release-age configuration value to a valid number, such as min-release-age=3, in the affected .npmrc files.

Guidance

  • Verify that all .npmrc files in the project have the correct min-release-age configuration value.
  • Update the min-release-age value to a valid number, such as min-release-age=3, in the ui/litellm-dashboard/.npmrc file.
  • Run npm install again in the ui/litellm-dashboard directory to test the fix.
  • Check for any other .npmrc files in the project that may be affected by this issue and update them accordingly.

Example

# Corrected .npmrc file
min-release-age=3

Notes

This fix assumes that the only issue is the invalid min-release-age configuration value. If there are other issues with the project's configuration or dependencies, additional troubleshooting may be necessary.

Recommendation

Apply the workaround by updating the min-release-age configuration value to a valid number, as this is a simple and effective fix for the reported issue.

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…
#generation error#database connection#vector store#embedding generation#cache error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING