Open chancehudson opened 1 month ago
It also works for me when I run cargo install --path .
. The reason that the cargo crate fails could be Triton-VM is on alpha releases now. Triton VM v0.42.0 (the next major version) should be ready within a few weeks. I think that'll fix this issue.
This was likely caused by tui-textarea's ratatui version spec, which would often select and incompatible ratatui version due to a spec like >= 0.23
. This would auto-update tui-textarea to an incompatible version even if your project had not yet taken that version. This should be fixed in tui-textarea 0.5 however (which has moved to stating deps as just e.g. 0.27
Two things to help diagnose this problem more generally:
cargo install --locked
will use the cargo lock file to choose the libs to use to build instead of taking the latest libscargo tree -i ratatui@version.x.y
will show you the dependency path to things
When i try to install this program from cargo i get the below output. I am able to install by cloning the repo and running
cargo install --path .