Closed e-oz closed 10 months ago
@e-oz Thanks for reporting, can you try setting NX_NATIVE_TASK_HASHER=false
and see if that helps?
For context, {workspaceRoot}
inputs are inclusive only. Having a negative one will do nothing.
In the previous version of the hasher, these kinds of inputs were mistakenly hashed, and the resulting hash was basically an empty string. The new hasher now will throw an error, but that was a mistake, and should show a warning instead. In the future this will throw a error though.
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.json
Expected Behavior
Was working fine in 17.1.3
GitHub Repo
No response
Steps to Reproduce
nx.json
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response