You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to the latest Nx version, i'm seeing that in a NestJS project, when a file change is detected, the previous build is not being cancelled, seems like all the builds happen at the same time and that makes the console to lose format. So if multiple file changes are made and there are build in progress, they will overlap.
Normally it should be something like this
But after a few concurrent restarts the console just starts outputting everything without line breaks.
I've tried adding a debounce timer for the serve executor, or disabling cache and parallelism in the build executor but the issue persists.
For now i've only seen this behavior in NestJS/Webpack build, the monorepo contains an angular project which behaves just fine.
Expected Behavior
The builds should be triggered in sequence in case changes are done in multiple files, other than that, even if they run in parallel, the console should not lose format.
GitHub Repo
No response
Steps to Reproduce
Create a NestJS project
Perform changes in multiple files fast (I reproduced it by adding and removing console logs in a file and saving with Ctrl+Z)
This is my current project.json, i added some options to see if i could debounce the builds but so far doesn't seem it is really using the debounce or the dependencies
Current Behavior
After upgrading to the latest Nx version, i'm seeing that in a NestJS project, when a file change is detected, the previous build is not being cancelled, seems like all the builds happen at the same time and that makes the console to lose format. So if multiple file changes are made and there are build in progress, they will overlap.
Normally it should be something like this
But after a few concurrent restarts the console just starts outputting everything without line breaks.
I've tried adding a debounce timer for the serve executor, or disabling cache and parallelism in the build executor but the issue persists.
For now i've only seen this behavior in NestJS/Webpack build, the monorepo contains an angular project which behaves just fine.
Expected Behavior
The builds should be triggered in sequence in case changes are done in multiple files, other than that, even if they run in parallel, the console should not lose format.
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
This is my current project.json, i added some options to see if i could debounce the builds but so far doesn't seem it is really using the debounce or the dependencies
The text was updated successfully, but these errors were encountered: