Installing with --no-dev fails #598

Closed
opened 2026-02-04 21:22:43 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @lommes on GitHub (Mar 12, 2018).

When you try to install BookStack with composer install --no-dev this will fail since some packages like barryvdh/laravel-ide-helper are not installed, but expected in config/app.php.

Installing with the no-dev option is a thing often used by deployment-systems. I use deployer and have to override some solid defaults to make it work. Also composer might change the way how they deal with packages in require-dev and only load require packages by default.

If the package is required for running BookStack it should be included in the required section. Are the entries in app.php still required or are these packages already using autodiscovery (at least laravel-ide-helper does)? If so, we can remove them.

Originally created by @lommes on GitHub (Mar 12, 2018). When you try to install BookStack with ```composer install --no-dev``` this will fail since some packages like barryvdh/laravel-ide-helper are not installed, but expected in config/app.php. Installing with the no-dev option is a thing often used by deployment-systems. I use [deployer](https://deployer.org/) and have to override some solid defaults to make it work. Also composer might change the way how they deal with packages in require-dev and only load require packages by default. If the package is required for running BookStack it should be included in the required section. Are the entries in app.php still required or are these packages already using autodiscovery (at least laravel-ide-helper does)? If so, we can remove them.
OVERLORD added the 🛠️ Enhancement🔧 Maintenance labels 2026-02-04 21:22:43 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Mar 12, 2018):

@lommes Yeah, I totally agree with the above.

It looks like all the third party providers have auto-discovery but I know for the PDF libs and Intervention I used non-default aliases/Facades since the defaults are very generic and could get confused with other classes. Not sure if that will have an impact and how auto-discovery works there.

@ssddanbrown commented on GitHub (Mar 12, 2018): @lommes Yeah, I totally agree with the above. It looks like all the third party providers have auto-discovery but I know for the PDF libs and Intervention I used non-default aliases/Facades since the defaults are very generic and could get confused with other classes. Not sure if that will have an impact and how auto-discovery works there.
Author
Owner

@ssddanbrown commented on GitHub (Mar 18, 2018):

Just pushed c6844324d0 to cover this.

I've left the non-dev service providers in there as it's nice to be able to see all required app service providers used listed in one place.

@ssddanbrown commented on GitHub (Mar 18, 2018): Just pushed c6844324d0e354e728b385b8d238780cd65052e7 to cover this. I've left the non-dev service providers in there as it's nice to be able to see all required app service providers used listed in one place.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#598