fix(misc): ensure plugins are not creating workspace context while creating nodes #22967
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 0cbad41. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
AgentEnder
force-pushed
the
fix/daemon-glob
branch
from
b3e8682
to
0cbad41
Compare
There was a problem hiding this comment.
Playwright is actually also broken.. but would be fixed if you convert all the functions in the WorkspaceContext to go to the daemon.
None of the calls to the workspace context should stay on the process unless the daemon is disabled or its on the daemon itself. Things like the Nx process should also go to the daemon to not do double work.
|
|
||
| const DAEMON_ENV_SETTINGS = { | ||
| NX_PROJECT_GLOB_CACHE: 'false', | ||
| NX_CACHE_PROJECTS_CONFIG: 'false', | ||
|
|
||
| // Used to identify that the code is running in the daemon process. | ||
| NX_ON_DAEMON_PROCESS: 'true', |
There was a problem hiding this comment.
I think we can set a global.NX_DAEMON = true on the Daemon Server
| export async function globAsync(globs: string[], exclude?: string[]) { | ||
| if (isOnDaemon() || !daemonClient.enabled()) { | ||
| return globWithWorkspaceContext(workspaceRoot, globs, exclude); | ||
| } else { | ||
| return daemonClient.glob(globs, exclude); | ||
| } | ||
| } |
There was a problem hiding this comment.
I think we can do this in the workspace-context.ts file.
Those functions should actually all go to the daemon...
Things like allWorkspaceFiles are also broken right now.
Could we change them all?
| export function isOnDaemon() { | ||
| return !!process.env.NX_ON_DAEMON_PROCESS; | ||
| } |
There was a problem hiding this comment.
This should probably live in the daemon directory?
…eating nodes
Current Behavior
Some plugins utilize
globWithWorkspaceContextto perform a glob search duringcreateNodes. This works fine without plugin isolation, and would still "work" with it, but when plugins are isolated they don't share a workspace context. Combine this with the daemon and we have issues.Expected Behavior
If the daemon is enabled, its workspace context is utilized when performing glob searches
Related Issue(s)
Fixes #