composer require currently downloads all the contents of the repository, but for production usage the development stuff is not required (and it could may be harmful if it contains executable files).
What about removing this development stuff from releases?
This affects only installing releases: git-cloning is not touched, so that people that want to run tests/build phars can perform a git clone
PS: I've been using this approach for more that one year for my projects, and both developers and end-users (and TravisCI) are happy :wink: (see for instance Punic)
composer require
currently downloads all the contents of the repository, but for production usage the development stuff is not required (and it could may be harmful if it contains executable files).What about removing this development stuff from releases?
This affects only installing releases: git-cloning is not touched, so that people that want to run tests/build phars can perform a
git clone