I made some attempts to resolve this issue, and eventually, I found that installing sui-move-analyzer with another command, while keeping all configurations unchanged, solved the problem.
By using this command to install move-analyzer and then renaming it to sui-move-analyzer, the issue was perfectly resolved.
So, is there a bug in the sui_move_analyzer branch?
When I use the sui-move-analyzer plugin in VSCode, I encountered the following issues:
My
Move.toml
:My VSCode
settings.json
:The command executed during the installation of sui-move-analyzer is:
I made some attempts to resolve this issue, and eventually, I found that installing sui-move-analyzer with another command, while keeping all configurations unchanged, solved the problem.
By using this command to install move-analyzer and then renaming it to sui-move-analyzer, the issue was perfectly resolved. So, is there a bug in the sui_move_analyzer branch?