Constrain Node version to <26#25
Merged
Merged
Conversation
anirudh-bijay-glean
requested review from
eshwar-sundar-glean,
garvit-scio,
mohit-gupta-glean and
swarup-padhi-glean
as code owners
eshwar-sundar-glean
approved these changes
Jun 23, 2026
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
2 participants
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.
What
Constrain supported Node.js versions to <26.
Why
On Node 26 the plugin's
tools/listrequest hangs and times out, so Claude Code drops the plugin's entire toolset. It turns out Node 26 bundles undici 8, which makesfetchuse HTTP/2 by default, and the plugin appears to receive the Glean gateway's response totools/listonly over HTTP/1.1 – over HTTP/2 it receives nothing.Prior versions of Node bundle
undici <=7and so do not offer HTTP/2 infetch.Code changes
>=22 <26) inpackage.json.