Skip to content

fix(misc): use workspaceRoot in workspaceModule path - #35142

Merged
AgentEnder merged 1 commit into
nrwl:masterfrom
djohnson-aperture:patch-1
Aug 10, 2026
Merged

fix(misc): use workspaceRoot in workspaceModule path#35142
AgentEnder merged 1 commit into
nrwl:masterfrom
djohnson-aperture:patch-1

Conversation

@djohnson-aperture

Copy link
Copy Markdown
Contributor

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.

@djohnson-aperture
djohnson-aperture requested a review from a team as a code owner April 1, 2026 23:10
@netlify

netlify Bot commented Apr 1, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 08ef134

@netlify

netlify Bot commented Apr 1, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 08ef134

@nx-cloud

nx-cloud Bot commented Apr 8, 2026

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit 08ef134

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 17m 12s View ↗
nx run-many -t check-imports check-lock-files c... ✅ Succeeded 6s View ↗
nx-cloud record -- pnpm nx-cloud conformance:check ✅ Succeeded 58s View ↗
nx build workspace-plugin ✅ Succeeded <1s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 17s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 5s View ↗

☁️ Nx Cloud last updated this comment at 2026-07-28 16:48:07 UTC

nx-cloud[bot]

This comment was marked as outdated.

@FrozenPandaz
FrozenPandaz requested a review from AgentEnder April 23, 2026 21:06
@FrozenPandaz FrozenPandaz added the priority: low Low Priority (does not affect many people or not severely or has an easy workaround) label Apr 23, 2026
@AgentEnder
AgentEnder force-pushed the patch-1 branch 2 times, most recently from 5826578 to 254fa7f Compare May 6, 2026 21:06
@AgentEnder AgentEnder changed the title Use workspaceRoot in workspaceModule path fix(misc): use workspaceRoot in workspaceModule path May 6, 2026
nx-cloud[bot]

This comment was marked as outdated.

@AgentEnder
AgentEnder force-pushed the patch-1 branch 2 times, most recently from 4773a72 to 1394be6 Compare May 8, 2026 03:02
nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

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.

@nx-cloud nx-cloud Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Nx Cloud View detailed reasoning in Nx Cloud ↗

🔔 Heads up, your workspace has pending recommendations ↗ to auto-apply fixes for similar failures.


🎓 Learn more about Self-Healing CI on nx.dev

@AgentEnder
AgentEnder merged commit 5ffd132 into nrwl:master Aug 10, 2026
18 of 19 checks passed
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: low Low Priority (does not affect many people or not severely or has an easy workaround)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants