🩹 fix: Correct Node Version and Install Command on the Local Install Hub - #754
Merged
berry-13 merged 1 commit intoSep 3, 2026
Conversation
The npm card on /docs/local advertised Node.js v20.19+ and `npm ci` as the install step. Both are wrong: - LibreChat pins Node 24.16.0 in .nvmrc and builds on node:24.16.0-alpine, and every /docs/local/npm guide already states v24.16.0. The card was the only remaining place claiming v20.19+. - LibreChat has no root postinstall, so `npm ci` installs workspace dependencies without building packages/data-provider, data-schemas, api, packages/client or the client bundle. `npm run backend` cannot start from that state. `npm run reinstall` (config/update.js -l -g) runs `npm ci` followed by `npm run frontend`, which is what the full guide instructs. Only untranslated structural data changed, so no locale dictionary is affected. Reported via Discord docs feedback 1545085630760095786 (/docs/local).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
berry-13
deleted the
berry-13/auto-librechat-ai-address-feedbacks-run-3-20260903T1800
branch
September 3, 2026 23:14
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The npm card on
/docs/localcarried two incorrect facts about installing LibreChat without Docker. Both are corrected against LibreChat's own source onorigin/dev.Node version. The card advertised
Node.js v20.19+. LibreChat pins24.16.0in.nvmrcand builds onnode:24.16.0-alpinein itsDockerfile, and every localized/docs/local/npmguide already statesv24.16.0. The hub card was the only place in this repository still claimingv20.19+, so it contradicted the very guide it links to.Install command. The card listed
cd LibreChat && npm cifollowed bynpm run backend. LibreChat has no rootpostinstall, sonpm ciinstalls workspace dependencies without buildingpackages/data-provider,packages/data-schemas,packages/api,packages/client, or the client bundle.npm run backendcannot start from that state. The canonical step isnpm run reinstall(node config/update.js -l -g), which runsnpm ciand thennpm run frontend, exactly what the full guide instructs.Both values live in the component's structural data, which is explicitly untranslated ("Brand titles, prereq labels, commands and bundled service names stay as written"). No locale dictionary or MDX translation is affected.
Feedback addressed
1545085630760095786-/docs/local/docs/local/npm, but the card that surfaces it on/docs/localstated the wrong Node version and an install command that cannot produce a runnable app. A reader on a low-end machine following that card would install Node 20 and then fail to start the backend.v24.16.0and its command list to thenpm run reinstallflow so it matches the guide it links to.Validation
pnpm install --frozen-lockfile- passed, lockfile unchangedpnpm run lint- passedpnpm run lint:prettier- passedpnpm run typecheck- passedpnpm test- passed (33 files, 391 tests)pnpm build- passed, and the prerendered/docs/localoutput was checked directly: one occurrence ofNode.js v24.16.0, zero ofv20.19,npm run reinstallpresent,npm cigoneNote: the first
pnpm buildon this base aborted with a V8heap out of memoryerror. It is a local heap-size artifact, not a code failure. The same build passed before the rebase and passes here withNODE_OPTIONS=--max-old-space-size=8192.Not changed
api/server/index.js, npm workspaces, a Node base image), so reimplementing the server in Python is an upstream product-architecture decision and is out of scope for the documentation site. No repository change here could serve it./docs/local/npmstates npmv11.16.0while LibreChat'spackageManagerfield pinsnpm@11.13.0. The docs read as a minimum for the npm 11 line rather than an exact pin, so this was left alone as an unverified discrepancy rather than changed speculatively.