Skip to content

Archived (unsupported) packages - JSONStream, leveldown & q etc. #1113

Closed

Description

@MikeMcC399

Situation

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

"responsive" would imply "able to provide fixes"

Archived repos

Current status, ticked if now removed from citgm:

This is not an exhaustive list of packages based on archived repos. They are just amongst the list of failing citgm tests.

Suggestion

Remove the corresponding entries

citgm/lib/lookup.json

Lines 46 to 50 in ff3ea4a

"JSONStream": {
"prefix": "v",
"skip": "win32",
"maintainers": "dominictarr"
},

citgm/lib/lookup.json

Lines 278 to 284 in ff3ea4a

"leveldown": {
"head": true,
"useGitClone": true,
"skip": ["ppc", "s390"],
"tags": "native",
"maintainers": ["ralphtheninja", "vweevers"]
},

citgm/lib/lookup.json

Lines 357 to 361 in ff3ea4a

"q": {
"prefix": "v",
"maintainers": "kriskowal",
"skip": ["win32", ">=21"]
},

cc: @dominictarr @ralphtheninja @vweevers @kriskowal

Activity

  1. MikeMcC399 commented on Aug 2, 2026

    @MikeMcC399
    ContributorAuthor

    Additionally

  2. MikeMcC399 commented on Aug 3, 2026

    @MikeMcC399
    ContributorAuthor

    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.

  3. changed the title [-]Archived (unsupported) packages - `JSONStream`, `leveldown` & `q`[/-] [+]Archived (unsupported) packages - `JSONStream`, `leveldown` & `q` etc.[/+] on Aug 5, 2026
  4. MikeMcC399 commented on Aug 10, 2026

    @MikeMcC399
    ContributorAuthor

    #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!

  5. ljharb commented on Aug 14, 2026

    @ljharb
    SponsorMember

    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.

  6. sxa commented on Sep 28, 2026

    @sxa
    Member

    @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 ...

  7. MikeMcC399 commented on Sep 28, 2026

    @MikeMcC399
    Author
  8. sxa commented on Sep 28, 2026

    @sxa
    Member

    Hopefully that will be resolved fairly soon under the work actively being done at the moment by Beth under #1143 :-)

  9. MikeMcC399 commented on Sep 28, 2026

    @MikeMcC399
    ContributorAuthor

    I also posted a summary to the release team issue list nodejs/Release#1182 2 weeks ago.

  10. sxa commented on Sep 28, 2026

    @sxa
    Member

    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.

  11. MikeMcC399 commented on Sep 28, 2026

    @MikeMcC399
    Author
  12. MikeMcC399 commented on Oct 5, 2026

    @MikeMcC399
    ContributorAuthor

    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 👍🏻

  13. MikeMcC399 commented on Oct 8, 2026

    @MikeMcC399
    ContributorAuthor

    Closing this issue now, since any known remaining issues are covered separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions