You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Archived (unsupported) packages - JSONStream, leveldown & q etc. #1113
The following source repos are archived, therefore it is no longer possible to report issues or to expect fixes. This means that they are unsupported and cannot fulfil the Hard Requirements
The maintainers of the module remain responsive when there are problems
#1114 received feedback that JSONStream should be kept, although so far there was no reasoning shared.
What about the other unsupported packages? Should I submit PRs to remove these, or does the team want to keep all unsupported packages? Please let me know!
The reasoning is that it's an npm package with a non-lowercase name. As long as nonzero such packages in citgm are covered, i have no particular feelings about JSONStream.
@MikeMcC399 I note that you've closed two of the three PRs due to a lack of response. I approved the q one so that's gone in and IMHO it's reasonable to remove those other two as well so I'd personally be happy to approve if you wanted to reopen them ...
I would like to see a release of citgm that supports Node.js 26 before I (re-)submit anything more though.
Noting also that I don't believe the v26.x bit being missing from package.json causes any significant problems running it on 26 as we already run on 26 successfully in the citgm-smoker jobs.
Activity
MikeMcC399 commentedon Aug 2, 2026
Additionally
MikeMcC399 commentedon Aug 3, 2026
I submitted #1114 to remove
JSONStream. If this is good, then I would follow up with other PRs to remove the other deprecated / archived packages.[-]Archived (unsupported) packages - `JSONStream`, `leveldown` & `q`[/-][+]Archived (unsupported) packages - `JSONStream`, `leveldown` & `q` etc.[/+]MikeMcC399 commentedon Aug 10, 2026
#1114 received feedback that
JSONStreamshould be kept, although so far there was no reasoning shared.What about the other unsupported packages? Should I submit PRs to remove these, or does the team want to keep all unsupported packages? Please let me know!
ljharb commentedon Aug 14, 2026
The reasoning is that it's an npm package with a non-lowercase name. As long as nonzero such packages in citgm are covered, i have no particular feelings about JSONStream.
sxa commentedon Sep 28, 2026
@MikeMcC399 I note that you've closed two of the three PRs due to a lack of response. I approved the
qone so that's gone in and IMHO it's reasonable to remove those other two as well so I'd personally be happy to approve if you wanted to reopen them ...MikeMcC399 commentedon Sep 28, 2026
sxa commentedon Sep 28, 2026
Hopefully that will be resolved fairly soon under the work actively being done at the moment by Beth under #1143 :-)
MikeMcC399 commentedon Sep 28, 2026
I also posted a summary to the release team issue list nodejs/Release#1182 2 weeks ago.
sxa commentedon Sep 28, 2026
Noting also that I don't believe the v26.x bit being missing from
package.jsoncauses any significant problems running it on 26 as we already run on 26 successfully in thecitgm-smokerjobs.MikeMcC399 commentedon Sep 28, 2026
MikeMcC399 commentedon Oct 5, 2026
citgm@10.0.3 was released on Sep 28, 2026 with support for:
"node": "^22.22.2 || ^24.15.0 || >=26.0.0"
so we can close off that discussion now 👍🏻
MikeMcC399 commentedon Oct 8, 2026
Closing this issue now, since any known remaining issues are covered separately.