Best Practices for Multiple Runs

[jwriteclub]

As I've been experimenting with Crystal, I've noticed two challenges (neither are problems with Crystal per-se, but with using it):

1. Non-committed code doesn't end up in the worktree -- specifically my node_modules folder doesn't get copied in (for a front end app)
2. My go.work file doesn't get copied in (which is important for developing with a forked version of a lib while the lib is under development alongside the app)
3. Port conflicts with running the dev server

While I can certainly have the "build" script install, this seems somewhat wasteful, and it probably makes more sense. For the go.work and port I don't know that there's an easy solution. I've built a little script that uses a file in a well known location to recreate these, and I can set it as the build script and it seems to get reliably run when a new worktree is created (so I can use a counter in the well known file to get the "next" port, so each instance has a private set of ports for testing).

I wonder if anyone else has faced these issues and if there's any best practices for this kind of environment setup stuff?