Skip to content

Backport Node SEA to v24.x #62119

Closed as not planned
#62190
Closed as not planned
Backport Node SEA to v24.x#62119
#62190
Labels
releaseIssues and PRs related to Node.js releases.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@sxzz
sxzz
opened on Mar 5, 2026

What is the problem this feature will solve?

PR #61167 was only partially backported to Node.js 24 (v24.14.0). The --build-sea flag and ESM entrypoints support are missing from v24.x. Downstream tools like tsdown rely on these features.

Ref: #61167 (comment)

What is the feature you are proposing to solve the problem?

Backport the remaining SEA features to v24.x, specifically:

What alternatives have you considered?

Requiring users to use Node.js v25.7.0+, but v24.x is the current LTS line and many users cannot upgrade.

Activity

  1. sxzz
    added
    feature requestIssues requesting new Node.js features.
    on Mar 5, 2026
  2. github-project-automation
    added this to Node.js feature requestson Mar 5, 2026
  3. github-project-automation
    moved this to Awaiting Triage in Node.js feature requestson Mar 5, 2026

  4. ranjuhasankhan commented on Mar 6, 2026

    @ranjuhasankhan
    ranjuhasankhan
    on Mar 6, 2026 · Hidden as spam
  5. himself65
    added
    releaseIssues and PRs related to Node.js releases.
    on Mar 9, 2026

  6. himself65 commented on Mar 10, 2026

    @himself65
    himself65
    on Mar 10, 2026
    Member

    /cc @nodejs/releasers

  7. himself65
    removed
    feature requestIssues requesting new Node.js features.
    on Mar 10, 2026
  8. Renegade334
    linked a pull request that will close this issue[v24.x backport] sea: add --build-sea and support ESM entry point #62190on Mar 10, 2026
  9. Renegade334
    removed this from Node.js feature requestson Mar 10, 2026

  10. khalidsaidi commented on Mar 25, 2026

    @khalidsaidi
    khalidsaidi
    on Mar 25, 2026 · Hidden as off-topic

  11. github-actions commented on Jul 20, 2026

    @github-actions
    github-actionsbot
    on Jul 20, 2026 – with GitHub Actions
    Contributor

    This issue has been marked as stale due to 90 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  12. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jul 20, 2026

  13. github-actions commented on Aug 20, 2026

    @github-actions
    github-actionsbot
    on Aug 20, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

  14. github-actions
    closed this as not plannedon Aug 20, 2026

  15. sxzz commented on Aug 20, 2026

    @sxzz
    sxzz
    on Aug 20, 2026
    ContributorAuthor

    bump

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

    releaseIssues and PRs related to Node.js releases.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions