Skip to content

Repository Should Be Archived #8068

@jacksonSingleton

Description

@jacksonSingleton

Clearly, we will not be seeing any new updates. As interesting as this project was, unless a new maintainer takes the helm, this project should be archived.

Allowing users to create new issues and PRs that will never be fixed may lead to confusion. I can imagine a number of hyper users/contributors would be willing to take over the project. Over 10 months since a dependabot commit and over two years since an actual release is clear enough.

This was such an interesting project and may be able to see a new light with all of the changes we've seen around the JS ecosystem in recent times. After 9 years, I've switched off of hyper and it's saddening to see. To prevent anyone writing up detailed issues or wasting time on working through PRs, I think it would be responsible to archive hyper in its current state until a new maintainer is willing to come along.

cc: @rauchg @LabhanshAgrawal

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