psalm/assets/psalm-phar/composer.json

{
	"name": "psalm/phar",
	"description": "Composer-based Psalm Phar",
	"license": ["MIT"],
	"require": {
		"php": "^7.1 || ^8.0"
	},
	"conflict": {
		"vimeo/psalm" : "*"
	},
	"bin": ["psalm.phar"],
	"config": {
        "platform-check": false
    }
}
Add executable PHP files to PHAR distribution Previously a user of the phar distribution would have to invoke psalm as `vendor/bin/psalm.phar`. This is different to the command given in the psalm documentation, `vendor/bin/psalm` I also copied all files from the psalm/phar repo into assets/psalm-phar, so that development can be concentrated in this repo. The travis-deploy-phar.sh should copy any changes made back into the psalm/phar.git repo. 2019-06-07 00:12:53 +02:00			`{`
			`"name": "psalm/phar",`
			`"description": "Composer-based Psalm Phar",`
			`"license": ["MIT"],`
			`"require": {`
Experiment with PHP 7.1 compatibility (#4421) * Experiment with PHP 7.1 compatibility * Let’s hop 2020-10-26 20:14:48 +01:00			`"php": "^7.1 \|\| ^8.0"`
Add executable PHP files to PHAR distribution Previously a user of the phar distribution would have to invoke psalm as `vendor/bin/psalm.phar`. This is different to the command given in the psalm documentation, `vendor/bin/psalm` I also copied all files from the psalm/phar repo into assets/psalm-phar, so that development can be concentrated in this repo. The travis-deploy-phar.sh should copy any changes made back into the psalm/phar.git repo. 2019-06-07 00:12:53 +02:00			`},`
Don't allow installation of psalm/phar and vimeo/psalm in the same project The scoped and non-scoped code don't work together. 2019-06-07 22:49:41 +02:00			`"conflict": {`
			`"vimeo/psalm" : "*"`
			`},`
Fix Phar platform check Fixes #4640 2020-11-20 17:08:40 +01:00			`"bin": ["psalm.phar"],`
Fix other check 2020-12-29 13:57:09 +01:00			`"config": {`
			`"platform-check": false`
			`}`
Add executable PHP files to PHAR distribution Previously a user of the phar distribution would have to invoke psalm as `vendor/bin/psalm.phar`. This is different to the command given in the psalm documentation, `vendor/bin/psalm` I also copied all files from the psalm/phar repo into assets/psalm-phar, so that development can be concentrated in this repo. The travis-deploy-phar.sh should copy any changes made back into the psalm/phar.git repo. 2019-06-07 00:12:53 +02:00			`}`