Closed antonversal closed 1 week ago
Hey @antonversal, thanks for the report. The way I thought about implementing this was through the tunnel exectutor. The idea is that the tunnel executor starts the serve target on the Forge app and all dependent Custom UI projects.
Having said that, the tunnel executor is quite experimental at this stage. There were some challenges around terminating all processes in one go and I didn't find the time to implement this properly.
Alternatively, you may be able to define your own nx:run-commands
executor on the Forge app project/s to start the serve processes and projects you need.
I am closing this in favor of https://github.com/toolsplus/nx-forge/issues/36, but let me know if you have any further questions.
Hey @tbinna ,
Thanks.
I'll leave the configuration here if someone needs it:
apps/forge-app/project.json
"targets": {
"tunnel": {
"command": "cd {projectRoot} && forge tunnel"
},
"start": {
"executor": "nx:run-commands",
"options": {
"commands": [
{
"command": "nx serve forge-app",
"prefix": "[FORGE]"
},
{
"command": "nx serve custom-ui",
"prefix": "[UI]"
},
{
"command": "nx tunnel forge-app",
"prefix": "[TUNNEL]"
}
],
"parallel": true
}
}
}
Hello, Thanks for the project.
It seems that
nx serve
only serves the forge app, not the custom app, and it does not start tunneling. Deploying and installing work just fine. Any change to the custom UI app does not start rebuilding, but changes to the forge app do.manifest.yml
: