You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(core): add multiple Nx version detection to nx report (#33599)
## Current Behavior
When multiple versions of the `nx` package are installed in a workspace
(e.g., due to a third-party package incorrectly depending on nx), users
have no visibility into
this issue through `nx report`.
## Expected Behavior
The `nx report` command now detects when other packages depend on a
different version of nx than the workspace version and reports this
clearly:
⚠️ Multiple Nx versions detected
Your workspace uses [email protected], but other packages depend on a different
version:
- some-package → @scope/tool → [email protected]
These packages should not have nx as a dependency. Please report this
issue to the package maintainers.
Run pnpm why [email protected] for more details.
This helps users identify and report problematic packages that bundle
their own version of nx.
## Related Issue(s)
N/A - This is a proactive improvement to help users diagnose workspace
issues.
// Make this required once bun adds programatically support for reading config https://github.com/oven-sh/bun/issues/7140
47
48
getRegistryUrl?: string;
@@ -148,6 +149,7 @@ export function getPackageManagerCommand(
148
149
run: (script: string,args?: string)=>
149
150
`yarn ${script}${args ? ` ${args}` : ''}`,
150
151
list: useBerry ? 'yarn info --name-only' : 'yarn list',
152
+
why: 'yarn why',
151
153
getRegistryUrl: useBerry
152
154
? 'yarn config get npmRegistryServer'
153
155
: 'yarn config get registry',
@@ -195,6 +197,7 @@ export function getPackageManagerCommand(
0 commit comments