dan-design
commented
1 month ago I believe I may have figured out the issue. On the fresh installs I've tried (after getting rid of the old node), Herd never cleaned up its env vars during uninstall, so never reran its scripts for node/nvm. Gonna try again in a bit after removing the path var and re-uninstalling and rebooting.
Platform
Windows
Operating system version
10
System architecture
Intel (x86)
Herd Version
latest
PHP Version
8.2
Bug description
This is supposed to be a simple time saver for setting up windows pc for laravel development. So far I've spent about four hours trying to get a pc set up and am still unable to get it working. I have a background in windows and linux system administration and I have been using laravel and tools like valet since v4.
I tried installing this on a windows pc that at one point was set up for development with php7.4 and nodejs 10. Years ago I set that up and I forgot this user was ever using that set up. Anyway eventually I got the php and composer stuff cleared up and working but that was a bit of a pain. I have no idea what to do about node it's a disaster. May have been installed with chocolatey or something in the past. NVM cli 'works' but npm isn't in the path, and the node version from nvm isn't either. Intead I get the old one. If I remove the path variable for C:\Program files\nodejs I get command not found errors for npm. if I put it back npm will never work because it's using node 10.
I am glad I did not opt for pro.
Steps to reproduce
No response
Relevant log output
No response