spatie / wordpress-ray

Debug with Ray to fix problems faster in WordPress apps
https://myray.app
MIT License
74 stars 14 forks source link

Keep only non-dev packages in repo #28

Closed szepeviktor closed 3 years ago

szepeviktor commented 3 years ago

It makes releases much smaller.

szepeviktor commented 3 years ago

kép

This is an interesting piece of change in the lock file. I've simply issued composer update --no-dev (Composer v2)

jeffreyvr commented 3 years ago

Just a quick note: The composer post install script has not been executed in this pull request, which leads to a couple of namespaces not being properly prefixed in vendor/symfony/var-dumper/Cloner/AbstractCloner.php.

szepeviktor commented 3 years ago

Thank you.

rm -rf vendor/ && composer install gives me

Generated optimized autoload files containing 1466 classes
> sed -i '' 's/'\''Symfony/'\''Spatie\\WordPressRay\\Symfony/g' ./vendor/symfony/var-dumper/Cloner/AbstractCloner.php
sed: can't read s/'Symfony/'Spatie\\WordPressRay\\Symfony/g: No such file or directory
Script sed -i '' 's/'\''Symfony/'\''Spatie\\WordPressRay\\Symfony/g' ./vendor/symfony/var-dumper/Cloner/AbstractCloner.php handling the post-install-cmd event returned with error code 2
freekmurze commented 3 years ago

I'll merge this in, and run composer again for to get the lowest version of dips

freekmurze commented 3 years ago

@szepeviktor @jeffreyvr I've prepared v1.2.1 on the master branch. It has not been released yet.

Could you both check if the current master is ok?

If followed these steps to prepare it: https://github.com/spatie/wordpress-ray#release-instructions-for-maintainers

jeffreyvr commented 3 years ago

Did a quick test, everything seems to be working.