Install Laravel Lang Packages, in --dev
mode?
#201
-
This project has grown quite a bit and now has numerous very useful packages. The specific question is: the package How would I avoid having unnecessary code in production and not have problems due to missing packages? This is because in |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Indeed, when packages were scarce, the bulk of them were destined for the For example, to be able to use the facade in production to get a list of installed localizations, you had to do the following: composer require laravel-lang/common --dev
composer require laravel-lang/locales But now the number of packages useful for production has outgrown the number of packages, and it turns out that the documentation recommends doing so: composer require laravel-lang/common --dev
composer require laravel-lang/locales laravel-lang/models laravel-lang/routes laravel-lang/json-fallback That is, it offers to manually install 4 dependencies in the I agree that it is time to remove the recommendation of the |
Beta Was this translation helpful? Give feedback.
Indeed, when packages were scarce, the bulk of them were destined for the
dev
area.For example, to be able to use the facade in production to get a list of installed localizations, you had to do the following:
But now the number of packages useful for production has outgrown the number of packages, and it turns out that the documentation recommends doing so:
That is, it offers to manually install 4 dependencies in the
production
area while leaving 5 packages in the