-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nx Cannot find project 'my-app' although package.json is present #13134
Comments
Can you run |
and an These results repeat if I run That leading path separator looks suspicious. |
Was that ☝🏻all you needed? Is this still blocked? |
Hey, sorry, haven't gotten back to this just yet. Looking at it now, can you try running again with the following two environment variables set?
|
Thanks for looking (I see btw that you are a fellow midwesterner!) Got a good stack trace from
Yeah.. that project.json file def does not exist :) |
It sounds like that file definitely should exist. If you look in workspace/angular.json is there a project definition that points to apps/my-app? |
ahhh sure enough. Hmm such a flurry I don't know how that got there. I only executed the couple lines I put in the repro-steps above. |
Latest findings... Environment variables set as above Same repro steps as above, i.e., create-nx-workspace* and create package.json Run No
* however this did give |
Yeah, in 15 you'd need to setup yarn / npm / pnpm workspaces to enable the project inference. We look at those patterns. |
This seems to work in earlier 15 like 15.0.3 but that did it. Just checking my understanding....
Maybe just a |
#13203 this should contain that info. I'm going to close this out since we diagnosed the issue successfully. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Nx "Cannot find" my project
Expected Behavior
I expect Nx to run my target in
apps/my-app/package.json
Steps to Reproduce
add
apps/my-app/package.json
continue
Failure Logs
As mentioned above
Environment
The text was updated successfully, but these errors were encountered: