fix(misc): use workspaceRoot in workspaceModule path - #35142
Merged
Conversation
👷 Deploy request for nx-docs pending review.Visit the deploys page to approve it
|
👷 Deploy request for nx-dev pending review.Visit the deploys page to approve it
|
djohnson-aperture
force-pushed
the
patch-1
branch
from
April 1, 2026 23:10
731e4b7 to
2146c2b
Compare
AgentEnder
approved these changes
Apr 8, 2026
Contributor
|
View your CI Pipeline Execution ↗ for commit 08ef134
☁️ Nx Cloud last updated this comment at |
AgentEnder
force-pushed
the
patch-1
branch
2 times, most recently
from
May 6, 2026 21:06
5826578 to
254fa7f
Compare
AgentEnder
force-pushed
the
patch-1
branch
2 times, most recently
from
May 8, 2026 03:02
4773a72 to
1394be6
Compare
djohnson-aperture
force-pushed
the
patch-1
branch
from
May 25, 2026 15:32
1394be6 to
15b98d8
Compare
meeroslav
approved these changes
May 27, 2026
djohnson-aperture
force-pushed
the
patch-1
branch
from
June 23, 2026 16:11
15b98d8 to
9d27bd7
Compare
djohnson-aperture
force-pushed
the
patch-1
branch
3 times, most recently
from
July 16, 2026 12:44
9201f05 to
3673dcd
Compare
AgentEnder
approved these changes
Jul 21, 2026
copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from.
Contributor
There was a problem hiding this comment.
Nx Cloud has identified a flaky task in your failed CI:
Since the failure was identified as flaky, the solution is to rerun CI. Because this branch comes from a fork, it is not possible for us to push directly, but you can rerun by pushing an empty commit:
git commit --allow-empty -m "chore: trigger rerun"
git push
🔔 Heads up, your workspace has pending recommendations ↗ to auto-apply fixes for similar failures.
🎓 Learn more about Self-Healing CI on nx.dev
polygraph-snapshot-app Bot
pushed a commit
that referenced
this pull request
Aug 11, 2026
copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from. ## Current Behavior Running the `copy-workspace-modules` from anywhere other than the root of the workspace results in `ENOENT: no such file or directory` for the package. ## Expected Behavior Running `copy-workspace-modules` should copy the modules successfully regardless of where the process is run from.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from.
Current Behavior
Running the
copy-workspace-modulesfrom anywhere other than the root of the workspace results inENOENT: no such file or directoryfor the package.Expected Behavior
Running
copy-workspace-modulesshould copy the modules successfully regardless of where the process is run from.