-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
laravel/framework as a dependency #49
Comments
Hello, |
It seems to be a problem... Do you know a package which has the expected behaviour and which works with both Laravel and Lumen ? |
Looking into it. |
There are 2 options that I see right now:
|
Hi and happy new year. Did you think about this? I've pushed a branch with the modifications for Lumen compatibility on my fork. |
Hi ! Happy new year to you too! Your commit is here : cdarken@0e7dbd5
Than I can check the used framework and performing a
I don't want to manage a new branch especially for Lumen ! I lose time with branches. When I add features, I code in master and then merge modifications manually on each branch... I have added this in the
But it seems there is no configuration file in Lumen... Just a question : how do you load my package in lumen and manage package configuration ? |
For loading a config file you copy it manually in
|
Ok... So I will finally create a new branch especially for Lumen with the according documentation. |
I'm using this package with Lumen. But because laravel/framework is specified as a dependency, it pulls the entire framework on
composer install
. I was wondering, maybe you can you limit the dependencies to separate Illuminate packages.The text was updated successfully, but these errors were encountered: