🍒 Cherry-Picked Nx v19.3 Updates

[🌊 Nx Core]

Allow multiple `readyWhen` in nx:run-command executor

When starting a process like a server using nx:run-commands, we typically use the readyWhen option to indicate readiness by checking the console output.

However, when starting multiple dev-servers in parallel, all servers need to be considered “ready” only once they’ve all started, and it’s unclear which will take the longest. This uncertainty can cause issues for dependent tasks, like e2e tests, which might proceed even if one server isn’t fully ready.

To address this, you can now wait for multiple outputs in the readyWhen option, ensuring the command is considered ready only when all specified strings have been outputted.

"start-e2e-servers": {
    "executor": "nx:run-commands",
    "options": {
        "commands": [
            "nx run my-host:serve",
            "nx run my-micro-frontend:serve",
        ],
        "readyWhen": ["localhost:4200", "localhost:4201"],
        "parallel": true
    }
}

[🧩 Plugins]

rspack Plugin Improvements

Loom New Plugin Version Release 🚀

[🌐 Nx Cloud]

GitHub Integration with Nx Cloud

Want to go further?

If you're looking to improve your Developer Experience, build AI Frameworks, or optimize your CI/CD pipelines with Nx, feel free to reach out — I'm always happy to share real-world setups and practical tips.

Build on Foundations,
Scale with AI.

I design AI-powered workflows and engineering foundations that make teams faster, happier, and more consistent.