Consistent "Failed to process project graph" #27285
Comments
|
I think it needs to be said that this is a little frustrating. I truly appreciate everyone's effort in pulling this tool together and maintaining it, but this is the second pretty significant regression (failure?) I've encountered this year. And the most frustrating part of all of this is that I don't even want to use Nx. I would like to use Lerna. In all seriousness, I think you should do one of the following:
Again, I really do appreciate the investment Nrwl is making in the monorepo tooling space and that at the end of the day Nrwl is a business that needs to make money. So make it clear, is it Nx or Lerna? And if Lerna is still a thing, then it should be independent of Nx. |
|
To reproduce in any project, add a dependency to The root cause of the issue appears to be in how they define their {
"name": "@yarnpkg/builder",
"version": "4.1.1",
"license": "BSD-2-Clause",
"bin": "./lib/cli.js",
"exports": {
".": "./lib/index.js",
"./cli": "./lib/cli.js",
"./package.json": "./package.json"
},
"dependencies": {
"@yarnpkg/cli": "^4.2.1",
"@yarnpkg/core": "^4.0.5",
"@yarnpkg/fslib": "^3.0.2",
"chalk": "^3.0.0",
"clipanion": "^4.0.0-rc.2",
"esbuild": "npm:esbuild-wasm@^0.15.15",
"semver": "^7.1.2",
"tslib": "^2.4.0"
},Does that make this a |
|
Probably related to our issue as well. We are using docusaurus docs and they recently introduced such depencency "react-helmet-async": "npm:@slorber/react-helmet-async@*",as a result, we'd started to receive ⚠️ Unable to construct project graph.
Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
The "nx/js/dependencies-and-lockfile" plugin threw an error while creating dependencies: Target project does not exist: npm:react-helmet-async@npm:@slorber/react-helmet-async@*
Error: Target project does not exist: npm:react-helmet-async@npm:@slorber/react-helmet-async@*
at validateCommonDependencyRules (/Users/xxx/frontend/node_modules/nx/src/project-graph/project-graph-builder.js:323:15)
at validateDependency (/Users/xxx/frontend/node_modules/nx/src/project-graph/project-graph-builder.js:314:5)
at /Users/xxx/frontend/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:214:80
at Array.forEach (<anonymous>)
at /Users/xxx/frontend/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:205:49
at Array.forEach (<anonymous>)
at /Users/xxxfrontend/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:203:72
at Array.forEach (<anonymous>)
at /Users/xxx/frontend/node_modules/nx/src/plugins/js/lock-file/yarn-parser.js:200:26
at Array.forEach (<anonymous>)This happens because this condition https://github.com/nrwl/nx/blob/master/packages/nx/src/project-graph/project-graph-builder.ts#L525 and this https://github.com/nrwl/nx/blob/master/packages/nx/src/project-graph/project-graph-builder.ts#L528 don't take into account such syntax. I'll try to come up w/ the solution |
Current Behavior
Expected Behavior
lerna runto workGitHub Repo
No response
Steps to Reproduce
lerna run(probably with esbuild involved)Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: