🍒 Cherry-Picked Nx v19.3 Updates
Exploring My Selected Features from Nx Releases
Who am I? Whether it's as a Software Engineer, Tech Lead, or Architect, if it involves software development, I'm in! My journey began in the realm of Java development, but I fully transitioned into the universe of JavaScript/TypeScript and its exciting toolset. I support companies through their software development cycle challenges by utilizing Nx monorepos, micro frontends, robust testing strategies, and a touch of Extreme Programming philosophy. Every day for me is like waiting for the next episode of my favorite series—filled with learning, sharing, and growing together. Indeed, I'm as passionate about coaching and sharing knowledge as I am about coding. I am the father of two incredible boys, and I am endlessly grateful to my wife for supporting my passion every day.
[🌊 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
[🌐 Nx Cloud]
GitHub Integration with Nx Cloud
