We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
if we use composer.json for bower, why .bowerrc not from composer.json?
"extra": { ".bowerrc": { "directory": "./libraries", "scripts": { "postinstall": "rm -rf ./jquery" } },
The text was updated successfully, but these errors were encountered:
Why not use composer a script instead?
Sorry, something went wrong.
Why not use special composer-extra-assets component? Read some value and write some value.
You can create a .bowerrc file and this plugin won't touch (overwrite) it. With that you can also change the directory or install scripts.
The reason why other values are read from composer.json is that they have to be merged from multiple composer.json
What do you think of that solution?
No branches or pull requests
if we use composer.json for bower, why .bowerrc not from composer.json?
The text was updated successfully, but these errors were encountered: