Trying to upgrade meteor windows 10 install to 1.10. Currently it is 1.9.2. And Chocolatey is v0.10.15.
When I try an upgrade in PowerShell as admin user, I get
PS C:\WINDOWS\system32> choco upgrade meteor Chocolatey v0.10.15 Upgrading the following packages: meteor By upgrading you accept licenses for the packages. meteor v0.0.2 is the latest version available based on your source(s). Chocolatey upgraded 0/1 packages. See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Then I decided to try the uninstall/install route
PS C:\WINDOWS\system32> choco uninstall meteor Chocolatey v0.10.15 Uninstalling the following packages: meteor meteor v0.0.2 The package meteor wants to run 'chocolateyuninstall.ps1'. Note: If you don't run this script, the installation will fail. Note: To confirm automatically next time, use '-y' or consider: choco feature enable -n allowGlobalConfirmation Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): y Removing the Meteor data directory... Chocolatey timed out waiting for the command to finish. The timeout specified (or the default value) was '2700' seconds. Perhaps try a higher `--execution-timeout`? See `choco -h` for details. meteor uninstall not successful. Error while running 'C:\ProgramData\chocolatey\lib\meteor\tools\chocolateyuninstall.ps1'. See log for details. meteor not uninstalled. An error occurred during uninstall: meteor uninstall not successful. Environment Vars (like PATH) have changed. Close/reopen your shell to see the changes (or in powershell/cmd.exe just type `refreshenv`). Chocolatey uninstalled 0/1 packages. 1 packages failed. See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). Failures - meteor (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\meteor\tools\chocolateyuninstall.ps1'. See log for details. If a package uninstall is failing and/or you've already uninstalled the software outside of Chocolatey, you can attempt to run the command with `-n` to skip running a chocolateyUninstall script, additionally adding `--skip-autouninstaller` to skip an attempt to automatically remove system-installed software. This will only remove the packaging files and not things like software installed to Programs and Features. If a package is failing because it is a dependency of another package or packages, then you may first need to consider if it needs removed as it is typically installed as a dependency for a reason. If you decide that you still want to remove it, head into `$env:ChocolateyInstall\lib` and find the package folder you want removed. Then delete the folder for the package. This option should only be used as a last resort. PS C:\WINDOWS\system32>
And now I get this
PS C:\WINDOWS\system32> meteor --version The system cannot find the path specified. PS C:\WINDOWS\system32>
The method of upgrading meteor should be properly and clearly documented on meteor.com. This has been a gap in meteor documentation for a long time. Currently this appears to be the most up to date migration documentation -
And I have wasted too much time at various stages trying to go from meteor version x to version y. With the result that my live meteor-driven website is stuck at version 1.8.1. Or if its a case that meteor doesn’t reliably function on Windows then this should be made clear.