PHP 7.0, 7.1, 7.2 support.
I really need the support for these PHP versions with Local 5.x.x. I have sites that doesn't run correctly with 7.1 so I need 7.0 to get it to run correctly so I can start upgrading.
Support biometric auth on macOS
Local throws a few admin prompts, regularly, and I miss not being able to use Touch ID, Apple Watch, or other forms of biometric auth. Instead, I have to type in my password. Other apps/admin notices allow bio auth, so I'm not sure why Local isn't able to. Anyway, not a needed feature but it would be a fab ease-of-use improvement.
Automatically Trust HTTPS Certificate after Site Creation
Forum post: https://localbyflywheel.com/community/t/automattic-https-ssl-provisioning/10015
Exclude Files API
Introduce an API or mechanism similar to .gitignore for ignoring files on import, export, push, or pull. Forum post: https://localwp.com/community/t/folder-exclusion/17233
Sync sites using Dropbox
It would be nice to move away from MAMP the only reason I still use it is because I can sync my sites between computers using dropbox with ease. This is a feature that has been ask for over and over again in the forums.
Watch for PHP changes
Currently Instant Reload only watches wp-content/plugins and wp-content/themes for changes to CSS files. During Theme development it would be very useful to also watch for changes to PHP files.
Replace Sequel Pro with Sequel Ace
The Sequel Pro project is not longer maintained. The community forked the project and created "Sequel Ace" ( https://github.com/Sequel-Ace/Sequel-Ace ). Is it possible to replace "Sequel Pro" with "Sequel Ace" on Local? For example: Change "Download Sequel Pro" button to "Download Sequel Ace" (and other button to open the database in Sequel Ace).
Pull only database so Git can continue to version files.
Request from WPE Support: If we had a way of only syncing the database while using Local this would allow Git to work alongside it so they get both advantages. Versioning files, while also allowing customers to deploy database changes without 1) contacting support, 2) logging in via SSH, importing, search & replacing etc. If we could push/pull only the database everything else is handled for them. It should be a pretty big QOL improvement.
Remember paid plugin license keys during push/pull
Every time sites are pulled to Local then pushed back to server, I always have to manually re-enter the license keys for all my paid plugins. I realize this is a problem with WP migrations in general, not just Local. But...if Local could cleverly solve it somehow, just like it has solved so many other WP annoyances, that would be awesome!
Support domain mapping for multisite
With Local 3.3.X there used to be a manual way that you could define SSL, .conf and hosts file entry so that a multisite could handle domain mapping. See https://localwp.com/community/t/local-router-error-message-on-multi-network-instance/1913/13 for details. With Lightning, whenever the main site is restarted, the custom .conf added to ~\AppData\Roaming\Local\run\router are deleted. At minimum, do not delete the custom .conf. More preferably, add a way to define related domains within the UI so that ssl, .conf and hosts entry are managed along with the main site by Lightning.