Forge dev loop fix

[davidbarna]

Hi,
I just want to let you know that Forge has undocumented (hence unsupported) flags that may improve your dev loop.

DISABLE_TTY gets rid of the "the input device is not a TTY" issue.
FORGE_TUNNEL_MOUNT_DIRECTORIES allows consumers to add volumes to the docker image run by forge tunnel. So you can add the root node_modules folder as a volume.

I think the following command would improve the dev loop for your mono repo:

DISABLE_TTY=true FORGE_TUNNEL_MOUNT_DIRECTORIES=$(cd \"$(dirname \"../../../\")\"; pwd)/$(basename \"$1\")node_modules:/app/node_modules forge tunnel -d

There is no guarantee that those flags will be kept in the future. But at the moment it's working for me as expected.

[tbinna]

Hey @davidbarna, thank you for those hints and details, that looks very promising. I will reference this issue in our Nx-based Forge tooling project as well.

Mind me asking if you are using Turborepo in your Forge projects or how you got here? This turborepo-based approach has been an experiment but we decided to go with Nx-based Forge tooling which seemed much more mature, provides built-in tooling for CLI utilities and build process configuration.

[davidbarna]

Hi @tbinna,
I simply use turborepo for all my personal projects. I haven't taken the time to investigate nx yet. Turborepo suits my needs for now.