Node dependency install error handling correction
Cluster 85297. Data as of
Nothing open on GitHub. Fix merged in #85537 on 13 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #85537. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #85537. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where unsuccessful Node dependency installation still reported success and exited with code 0 is being addressed. These items relate to making the install process correctly surface and propagate errors when Node dependencies cannot be installed.
Open issues0
Open PRs0
Fixes on record
-
#85537 fix(install): a failed Node dependency install now fails the install instead of printing success
files:
scripts/install.sh,tests/test_install_sh_node_deps_failure.py,tests/test_install_sh_node_npm_check.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#85397 fix(install): fail when Node dependencies cannot install · merged via another change →
#85537,#77642
Closed issues · 1
- Closed#85297[Bug]: install.sh prints "Installation Complete!" and exits 0 after install_node_deps fails, leaving no node_modules
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #85537
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Aug 2026