Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The open PR (#65) for adding NX to the blues stack got me most of the way there. I've based most of my work off of @vsavkin's work in that PR with a few more changes to make it work in my application a little better.
I've added a dependency on nodemon to allow restarting the node process when esbuild builds a new server.js. I bet there is a way to do this in NX natively, but I was struggling to figure that out. So now NX manages starting all of the processes that do the watching themselves.
The update to the deploy.yml is to work around an issue where nx tries to scan the postgres folder when it doesn't have permissions to. By shifting the build to before attaching the database, we don't have this issue anymore. nrwl/nx#10244
With these pieces in place, I've been extremely happy with my development flow. I'm able to launch a vscode debug config that watches both server and client and reacts very quickly to changes. Just wanted to share my current implementation.