You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just ran this on one of my own libraries to see how it would work (neat, btw!) and found that it pulled in development dependencies into the generated phar. It would be nice to have an option to leave off dev dependencies from the built phar file. It would be nicer still to (eventually) have that be the default and there be an option to explicitly include dev dependencies.
The text was updated successfully, but these errors were encountered:
This would help keep the size of generated phar files down, as dev dependencies can be quite large at times. My own small library that I did a test build of this on created a phar four megabytes large. While it has some dependencies of its own, most of that is the dev deps.
I just ran this on one of my own libraries to see how it would work (neat, btw!) and found that it pulled in development dependencies into the generated phar. It would be nice to have an option to leave off dev dependencies from the built phar file. It would be nicer still to (eventually) have that be the default and there be an option to explicitly include dev dependencies.
The text was updated successfully, but these errors were encountered: