-
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_VERSION_CHANGED for format:write without any further text #29446
Comments
So it's funny, i was able to solve this issue by adding So I tried many time to run |
Actually after few more issues i figured out that just needed to disable daemon:
|
However I'd like still to keep this issue open in a hope that someone from nx team can check why daemon in a hook is different from a daemon in a root package and NX_VERSION_CHANGED error occurs |
I just got this error and don't know what to do to resolve
|
@bbecker-te did you try to stop the daemon or ignore it with |
Could you provide a minimal repro that I can clone to check the issue? That will increase the chances I can repro & fix this :) |
Current Behavior
I mirgrated to a new NX version using
nx migrate latest
including post-install and run-migrations.At same time I'm using following husky hook which just worked perfectly:
So now when I try to commit a change I have some weird error:
If I run nx format:write command separately - it just works. So it does not work from inside the hook.
Unfortunately --verbose flag is useless. nx reset also doesn't not help. Using npx nx also doesn't change anything. Please help!
Expected Behavior
Well nx should work also from git hooks and it should not be impacted by a version change.
I think this check is not working well. Also would be nice even if it's error to have more meaningful explanation
GitHub Repo
No response
Steps to Reproduce
Not sure if you can. But try this.
That's what i did..
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: