Skip to content
This repository was archived by the owner on Apr 28, 2025. It is now read-only.

Comments

Switch to nx#93

Closed
andyeskridge wants to merge 3 commits intoremix-run:mainfrom
andyeskridge:switch-to-nx
Closed

Switch to nx#93
andyeskridge wants to merge 3 commits intoremix-run:mainfrom
andyeskridge:switch-to-nx

Conversation

@andyeskridge
Copy link

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.

@MichaelDeBoey
Copy link
Member

@andyeskridge I suggest you to join forces with @vsavkin on #65, since he started first on this idea.
You can add suggestions on his PR and/or create a PR against his branch (on his repo).

This way we can focus on keeping all related discussions on the same PR.

@MichaelDeBoey MichaelDeBoey added the duplicate This issue or pull request already exists label Jun 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

duplicate This issue or pull request already exists

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants