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 was wondering about the purpose of the dependency folder. Would it make sense to remove it, add the dependencies to composer.json, and use the Composer autoloader instead?
A build of the package could be done with composer install --no-dev, ensuring that dependencies are properly managed.
Are there specific reasons why you chose to include the extra folder? I'd love to understand the reasoning behind it.
Thanks!
The text was updated successfully, but these errors were encountered:
I was wondering about the purpose of the dependency folder. Would it make sense to remove it, add the dependencies to
composer.json
, and use the Composer autoloader instead?A build of the package could be done with
composer install --no-dev
, ensuring that dependencies are properly managed.Are there specific reasons why you chose to include the extra folder? I'd love to understand the reasoning behind it.
Thanks!
The text was updated successfully, but these errors were encountered: