Closed jimlloyd closed 5 months ago
I was able to diagnose and fix the primary problem. My method was to simply try to use yarn to install and the discover that it reported errors that clearly should be fixed. After fixing all of those errors, bun nx ...
commands are working.
@Jordan-Hall no need to follow up. Thanks for doing this integration, it would be painful to have to give up bun.
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
The following error occurs for a variety of
bun nx ...
commands. For example:Note that I am in the process of migrating an existing
bun
monorepo project to usenx
. After a few false starts I was able to get to the point where I could runlint
on each package. I had not been running eslint previously so I found and fixed many warnings and errors, and in particular found and fixed multiple instances of cyclic dependencies (which made me very happy).But oddly, I got to the point where all packages passed lint (i.e.
bun nx run-many --target=lint --all=true --with-deps=true
was successful), and then committed about a dozen different files that had been modified with my last set of changes, and that somehow caused this problem.Expected Behavior
No error.
GitHub Repo
https://github.com/memento-ai/Memento
Steps to Reproduce
I also tried to rollback to prior commits where
nx lint
was working, but I had been working with multiple modified files. The problem only occurred after committing all files. I did this with a series of commits, but did not runnx lint
again during the process of committing, and was unable to figure out if there was a particular commit that caused the breakage.My efforts to rollback and fix were done in the branch
temp-1a2e107
. The commit1a2e107
is in the history ofnx-try-3
.Nx Report
Failure Logs
No response
Package Manager Version
bun: 1.1.12 or 1.1.13
Operating System
Additional Information
Probably related to #26053