Skip to content

Laravel Valet Windows 3 [v3.0.0]

Choose a tag to compare

@yCodeTech yCodeTech released this 21 Sep 01:27
· 229 commits to master since this release

The first official release of Laravel Valet Windows 3!

This has lots of updates and features that wasn't previously available in cretueusebiu/valet-windows. Most notable:

  • Added multi-PHP support, with the ability to easily change PHP versions, and per-site PHP version isolation (feature PR by @iamroi in cretueusebiu#195).
    • Enables the use of the previously disabled use command, to switch the default PHP version used by Valet.
    • Adds new commands php:add, php:remove, php:install, php:uninstall, php:list, xdebug:install, xdebug:uninstall.
  • Added PHP version to the links command output (Patch 1 PR by @damsfx in iamroi#1).
  • Added PHP version to the parked command output, improvements to the Patch 1 above and a new command php:which (Patch 2 by @yCodeTech in #1).
  • Added Valet Root CA generation and sign TLS certificates with the CA (PR by @shawkuro in cretueusebiu#179).
  • Added new command sudo that is the equivalent to the macOS command.
  • Fixed #3 where upon a fresh installation of Valet with no config.json, it would try to read the config even if it's not yet created and spits out an "Failed to open stream: No such file" error. Fixed by adding a check to see if the file exists in the read function of the Configuration class (fix PR by @hemant-kr-meena in #4).
  • Lots of removal of deprecated code and files.
  • Lots of refactoring and formatting.
  • Massive overhaul of the Xdebug installation behaviour: no longer auto installs, and a flag must be present in the command to install it.
  • Massive overhaul of diagnose command.
  • Improved UX by adding a progress bar UI to certain commands with long wait times.
  • Lots of bug fixes, and other changes.

For the complete details please read the Changelog.

Command Parity

Laravel Valet Windows 3 hopes to achieve as much parity as possible with the original macOS version, and as such, you can view the command parity checker. As of this release, we are at 87% out of a total 92% possible parity (out of a total 39 commands, 36 are possible for parity, with 34 complete).