Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix [Docs]: CONTRIBUTING says Node.js 18+, but package.json requires Node >=20 [2 pull requests, 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
NousResearch/hermes-agent#11684•Fetched 2026-04-18 05:59:24
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
WadydXWadydX
Participants
WadydXWadydX
Timeline (top)
cross-referenced ×2

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Likely docs drift after dependency/runtime baseline changed in package metadata.

Fix Action

Fixed

PR fix notes

PR #11690: docs(contributing): align Node prerequisite with package engines

Description (problem / solution / changelog)

Summary

  • Update contributor prerequisites from Node.js 18+ to Node.js 20+ in:
    • CONTRIBUTING.md
    • website/docs/developer-guide/contributing.md
  • Clarify both lines as matching root package.json engines (>=20.0.0)

Why

Contributors and docs-site readers could follow stale Node 18 guidance and hit avoidable setup/runtime mismatches.

Closes #11684

Changed files

  • CONTRIBUTING.md (modified, +1/-1)
  • website/docs/developer-guide/contributing.md (modified, +1/-1)

PR #11698: docs: align contributing node version with package engines

Description (problem / solution / changelog)

Summary

  • update the contributor prerequisites in CONTRIBUTING.md from Node.js 18+ to Node.js 20+
  • mirror the same fix in website/docs/developer-guide/contributing.md
  • note that the docs now match the root package.json engine requirement

Verification

  • compared CONTRIBUTING.md and website/docs/developer-guide/contributing.md against package.json ("engines": { "node": ">=20.0.0" })
  • searched the repo to confirm the contributing docs no longer mention Node.js 18+

Closes #11684

Changed files

  • CONTRIBUTING.md (modified, +1/-1)
  • website/docs/developer-guide/contributing.md (modified, +1/-1)

Code Example

"engines": {
    "node": ">=20.0.0"
  }
RAW_BUFFERClick to expand / collapse

Bug Description

Developer docs and enforced runtime requirements disagree on Node.js minimum version:

  • CONTRIBUTING.md says Node.js 18+
  • root package.json enforces "node": ">=20.0.0"

This can send contributors down the wrong setup path and cause avoidable install/runtime friction.

Steps to Reproduce

  1. Open CONTRIBUTING.md and check prerequisites table.
  2. Open root package.json and check engines.node.
  3. Compare values.

Expected Behavior

Documentation should match enforced repo requirements (single source of truth for minimum Node version).

Actual Behavior

Docs state Node 18+, while package metadata enforces Node >=20.

Affected Component

  • Setup / Installation
  • Documentation (config/setup guidance)

Messaging Platform (if gateway-related)

  • N/A (CLI only)

Debug Report

N/A (documentation consistency issue).

Operating System

N/A (docs mismatch is platform-independent)

Python Version

N/A

Hermes Version

0.10.0

Additional Logs / Traceback (optional)

Evidence:

  • CONTRIBUTING.md prerequisites row currently says: Node.js 18+
  • package.json: 
    "engines": {
  "node": ">=20.0.0"
}

Root Cause Analysis (optional)

Likely docs drift after dependency/runtime baseline changed in package metadata.

Proposed Fix (optional)

Update CONTRIBUTING.md to match package.json (Node.js 20+) and optionally note where Node is required vs optional.

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

extent analysis

TL;DR

Update the CONTRIBUTING.md file to reflect the minimum Node.js version as 20+ to match the package.json engines specification.

Guidance

  • Verify the current minimum Node.js version required by the project by checking the engines.node field in package.json.
  • Update the CONTRIBUTING.md file to match this version, ensuring consistency between documentation and project requirements.
  • Consider adding notes on where Node.js is required versus optional to clarify setup instructions for contributors.
  • Review other documentation files for similar inconsistencies to ensure a single source of truth for project requirements.

Example

No code snippet is necessary for this fix, as it involves updating documentation. However, the corrected CONTRIBUTING.md might include a line like: "Node.js 20+ is required for development and contribution."

Notes

This fix assumes that the package.json specification is the authoritative source for project requirements. If there are other dependencies or configurations that might affect the minimum Node.js version, those should be considered before making changes.

Recommendation

Apply the workaround by updating CONTRIBUTING.md to match the package.json specification, as this ensures documentation consistency and clarity for contributors without requiring a version upgrade that might not be necessary for all users.

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…
#installation#callback error#memory management#API rate limit#retriever 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