We have artisan command to publish the assets(CSS, JS,..). Something like this should work. php artisan asset:publish –path=”vendor/twitter/bootstrap/bootstrap/css” bootstrap/css php artisan asset:publish –path=”vendor/twitter/bootstrap/bootstrap/js” bootstrap/js i am not sure about the path.. But this should work.
Lets look at composer why or composer depends command. This command shows which other packages depend on a certain package. Show usage This is usage example $ composer depends psr/log symfony/debug v3.2.2 requires psr/log (~1.0)
Using –prefer-dist worked: composer install –prefer-dist to force dist part, which @ivoba mentioned; it seems default switch which uses git is –prefer-source.
You should use a specific ( tagged stable at best ) version wherever possible. While composer.lock does lock the dependency to a specific commit even when using dev-master … every composer update will update the dependency to the latest version and afterwards update the lockfile. If your lockfile somehow gets deleted/lost and it is not … Read more
Unfortunately* Composer doesn’t support Git submodules, as the main aim of Composer is to provide a similar inter-project dependency functionality and it would be pointless to try to replicate submodules in Composer. I have the same problem that you are trying to solve, of developing a library while simultaneously developing the application that uses that … Read more
Smells like a Cap 3 bug. I suggest just guaranteeing you are where you want to be from the shell perspective: execute “cd ‘#{release_path}’; #{fetch(:composer_command)} install”