Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

discuss the future of Nx plugin #951

Open
vmasek opened this issue Mar 2, 2025 · 2 comments
Open

discuss the future of Nx plugin #951

vmasek opened this issue Mar 2, 2025 · 2 comments
Assignees

Comments

@vmasek
Copy link
Collaborator

vmasek commented 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.

@vmasek vmasek self-assigned this Mar 2, 2025
@BioPhoton
Copy link
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

@vmasek
Copy link
Collaborator Author

vmasek commented Mar 5, 2025

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

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants