Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@utarwyn have a look at https://github.com/phillipCouto/nx-go/commits/issue-151-shell-invalid-cwd/?since=2025-08-24&until=2025-08-24

1. I fixed the e2e tests to use the correct cwd. The reason we were seeing the spawn /bin/sh ENOENT error is because the cwd was pointing to a folder that does not exist. This is because the runNxCommandAsync would just add the projected cwd to the cwd the e2e command was running from and not the cwd within the workspace we created for the test.

2. Created a utility to compute the cwd which will also be the root of the target project. Using the workspace root plus the root of the project so we can be within the target project folder regardless of where the user is executing the command within the workspace.

3. Updated the generator to configure the targets correctly with the assumption we are running executors within the projects root consistently.

4. Updated tests to now properly expect the command string factoring the consistent evaluation of cwd being the root of the project.

If you move ahead with my changes this will be a new major release as existing targets assuming the old cwd behaviour will need to be updated.

@utarwyn have a look at https://github.com/phillipCouto/nx-go/commits/issue-151-shell-invalid-cwd/?since=2025-08-24&until=2025-08-24

1. I fixed the e2e tests to use the correct cwd. The reason we were seeing the `spawn /bin/sh ENOENT` error is because the cwd was pointing to a folder that does not exist. This is because the `runNxCommandAsync` would just add the projected cwd to the cwd the e2e command was running from and not the cwd within the workspace we created for the test.

2. Created a utility to compute the cwd which will also be the root of the target project. Using the workspace root plus the root of the project so we can be within the target project folder regardless of where the user is executing the command within the workspace.

3. Updated the generator to configure the targets correctly with the assumption we are running executors within the projects root consistently.

4. Updated tests to now properly expect the command string factoring the consistent evaluation of cwd being the root of the project.

If you move ahead with my changes this will be a new major release as existing targets assuming the old cwd behaviour will need to be updated.

@utarwyn did you have a chance to look into my patch?