Reproduction
-
Open a new folder in VSCode and run rojo init in the terminal to make a rojo project.
-
In the terminal, install rojo via Aftman in any of the following ways:
- Running
aftman add rojo
- Installing rojo via the Rojo Command Pallete menu (CTRL+Shift+P)
- Creating an
aftman.toml file and add the following lines:
[tools]
rojo = "rojo-rbx/rojo@7.4.4" # replace 7.4.4 with latest or preferred version
- Open the Command Palette (CTRL+Shift+P) and open the Rojo menu. The Rojo extension sees Rojo as installed:

-
Now rename aftman.toml to rokit.toml. (Both files support the same format)
-
Open the Command Palette again and open the Rojo menu. The Rojo extension now sees Rojo as not installed:

- Navigate to the Install Rojo now option and click it. The Rojo extension should now be installed via both Aftman and Rokit:

Explanation
Rojo can detect its own installation via Aftman but not via Rokit.
This issue may also require some feedback:
- During installation the user could be asked which toolchain manager they prefer (Foreman, aftman, rokit)
- The extension could also choose to prefer rokit in new projects as rojo seems to be pushing people to migrate to their tool
- Should the extension should a migration popup like the one shown when Foreman is installed?
This is related to #91. I have not checked if #94 addresses all the issues in this post
Reproduction
Open a new folder in VSCode and run
rojo initin the terminal to make a rojo project.In the terminal, install rojo via Aftman in any of the following ways:
aftman add rojoaftman.tomlfile and add the following lines:Now rename
aftman.tomltorokit.toml. (Both files support the same format)Open the Command Palette again and open the Rojo menu. The Rojo extension now sees Rojo as not installed:
Explanation
Rojo can detect its own installation via Aftman but not via Rokit.
This issue may also require some feedback:
This is related to #91. I have not checked if #94 addresses all the issues in this post