📗 docs: Refresh Node 24 Development Guidance

[danny-avila]

Summary

I updated the LibreChat npm and development documentation to match the current Node 24 guidance and refreshed contributor-facing development references from the repo agent instructions.

• Updated npm-based setup docs to recommend Node.js v24.16.0 and npm v11.16.0.
• Added nvm setup and version verification steps for local development and npm installation.
• Replaced stale Node 20/openid-client compatibility guidance in local, development, and remote docs.
• Updated clean install guidance to use npm run reinstall after Node/npm changes and npm run smart-reinstall for normal updates.
• Refreshed development overview, architecture, conventions, and testing docs with current workspace boundaries, TypeScript direction, command usage, naming conventions, and testing philosophy.
• Updated the image generation MCP global module example path from Node 20 to Node 24.

Change Type

• Documentation update

Testing

I validated the edited docs and production docs build locally.

Test Configuration:

• Node.js: v24.16.0
• npm: v11.16.0
• Package manager: pnpm 9.5.0

Commands run:

git diff --check
rg -n "v20\.19\.0|20\.19\.0|22\.12\.0|>= 23\.0\.0|node/v20|NPM" content/docs
pnpm build

The build passed. It still reports the existing Browserslist data-age warning, unrelated to these docs changes.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have made pertinent documentation changes
• My changes do not introduce new warnings

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
librechat-ai	Ready	Preview, Comment	Jun 1, 2026 1:49pm

[github-actions]

📦 Next.js Bundle Analysis for librechat.ai

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌