So if you happen to insert invalid version string when requiring package, it will still write it into composer.json and nothing works after that. So for example; composer require phpunit/phpunit:"8.3.3 as ^8.3"

My composer.json:

{
    "require": {
        "phpunit/phpunit": "8.3.3 as ^8.3"
    }
}

Output of composer diagnose:

$ composer diagnose
        

Under the 'Theme' settings tab you can upload images. It would be great if vector images can be added so it can scale without causing artifacts.

Installation of Laravel Zero with the command below

laravel-zero new TestApp

Results in output

Writing lock file
Generating optimized autoload files
> @php application app:rename
Renaming the application...

 What is your application name?:
 >

  Aborted.


Script @php application app:rename handling the post-create-project-cmd event returned with error code 1
Applicati

SMProxy的账号密码端口和ip能设置与原mysql一样的吗?比如都设置为 127.0.0.1 root 123456 3306
目的是为了防止这个访问突然断了后直接连回mysql,或者说这服务有守护进程在的吗?服务挂了会重启或服务器挂了重启它也跟着重启而不需要手动启动

As per my comments in #1162:

• Deprecated features should be a warning
• Removed features should be an error
• New features should be an error
• For the few things which don't fall in the above categories: whether it is an error/warning should depend on how PHP handles the issue, i.e. does it cause a PHP parse/fatal error or a notice or warning to be thrown ?

Similarly for the error

It would be great to handle subgroups/subfolders as the following image: