Skip to content

Plan for transition to ESM? #1770

@nwalters512

Description

@nwalters512

@octokit/core and friends are now ESM-only. The packages here that use them, like @actions/github, are still on the previous major version of @octokit/core (which uses CommonJS).

Presumably the @actions/* packages will need to switch to the new versions eventually to keep up with new features, fixes, API endpoints, and so on. What's the plan for doing so? Is this project looking for community help with that work?

ESM-only can be a reasonably disruptive change. Since the official @octokit/* packages are moving in that direction, I'll assume GitHub has already discussed this internally and decided that this work is work the risks and disruption to users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions