@piersg When browsing the npm versions for the package I notice that the version tagged "@next" is an earlier version but the CRM Development page in HS when enrolled in the beta tells me to download using the next suffix. Is this information outdated, and should I just use the latest package instead?
@JohanL - Any chance you have another computer that you can try to install on. I find it suspect that you get the same results even in a virtual box. Perhaps the Mac m1 chip might be the issue, or running the terminal in Rosetta. It's possible there are some dependency binaries that aren't compatible with m1.
I would also try to install nvm and try a slightly older version of node if you can, as well as maybe an older version of the CLI like 3.0.10
Thanks for you reply. I actually got it going after figuring out that the npm package tagged "next" is an older beta and not the latest release of the cli client. It seems the information found some places on HS that one ought to install the "@next" version is outdated. I'm just keeping this thread alive a bit longer to maybe get final confirmation on this.
Hi, @JohanL. Thanks for reaching out. It's not 100% clear if we can troubleshoot this one with the available information. Hey, @piersg, do you have any good first troubleshooting steps for @JohanL in getting the HS CLI set up?
@piersg When browsing the npm versions for the package I notice that the version tagged "@next" is an earlier version but the CRM Development page in HS when enrolled in the beta tells me to download using the next suffix. Is this information outdated, and should I just use the latest package instead?