aaP_hareeshnarayan1982 Thanks for your reply and suggestion. Yes obviously the problem is the NPM and Node.js installation didn't make its way to PATH. While using Fedora (unsupported by default from Aapanel officials), their installation script works flawlessly, and I could use any version of Node.js I want to be used in command line.
The problem happened when I tried to use AlmaLinux as my base system installation (supported (?) by Aapanel), the Node.js installation script (or command line version setter) didn't work as expected. I tried on regular amd64 and aarch64 machine, yet it still unsuccesful. By setting the export PATH manually, yes it can be solved, but when we need to update the installation, we need to always double check the .bash_profile
(or anything used to set its export PATH), make it inconvenience.
But for now, maybe that's the only way to make it works...