Skip to content

Proposal to transfer the Corepack repo into the Node.js organization #558

Closed
@arcanis

Description

@arcanis

The PR at nodejs/node#35398 adds a new dependency into the Node trunk: Corepack. Since once the PR has landed the expectation is that people will only use it through Node, I believe it would make sense to move it inside the Node organization.

Maintenance:

I would be ready to keep maintaining Corepack regardless the org it belongs to, especially given the low scope (cf next section), but it would let you have a better control on what the supported workflows and integrations.

Roadmap:

Corepack is expected to stay very simple, with a low amount of features. My expectation is that it's already almost feature-complete. As a result, the roadmap will mostly be to fix launch bugs, and keep the codebase in line with the Node deprecations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    approvedRequest approved by TSC/CommComm

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions