Skip to content

discuss the future of Nx plugin #951

Closed
Closed
discuss the future of Nx plugin#951
Assignees
vmasek

Description

@vmasek
vmasek
opened on Mar 2, 2025

There seems to be a reason why Nx team is not moving towards adding ESM support for plugins as is, the reason is recently announced switch of core Nx tech stack to Rust, they will be introducing a new API for task execution which (I currently assume) will offer much more flexibility to do plugins.

Activity

  1. vmasek
    self-assigned this
    on Mar 2, 2025

  2. BioPhoton commented on Mar 4, 2025

    @BioPhoton
    BioPhoton
    on Mar 4, 2025
    Collaborator

    Some additional info:

    • The reason to not switch to ESM is the effort it takes. The bet it on latest node features and a future execution of TS directly.
    • The new APIs are add ons for existing tasks.
    • Only the core will be rewritten in rust. the rest remains in TS for the community

  3. vmasek commented on Mar 5, 2025

    @vmasek
    vmasek
    on Mar 5, 2025
    CollaboratorAuthor

    Yes, my formulation was little bit rough, what I meant is "executors will not be ESM" because "there will be no more explicit executors as we know them".
    What I hope for is that new API will support ESM plugins as that is highly requested feature

  4. BioPhoton commented on Aug 13, 2025

    @BioPhoton
    BioPhoton
    on Aug 13, 2025
    Collaborator

    Close this as we need plugin for --cache options automation. see #1059

  5. BioPhoton
    closed this as completedon Aug 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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