Egge on Nostr: The first thing is the tooling. I switched from npm to yarn, because I felt like it ...

The first thing is the tooling. I switched from npm to yarn, because I felt like it had the better workspace support. But of course this introduces other issues, like adding some stuff to your dockerfile, changing commands, etc.

Then the worst part was making sure that the packages referenced each other in the right way. I have one package "env" that contains a script that will create an .env file for you. But of course this needs to be created in the root directory of the repo, not in the packages dir. Same thing with the webserver that needs to serve the output of another packge.

I ended up adding ROOT_DIR=$(pwd) to all scripts and referenced that env var in each package.