Comments (4)
Normally you only have to do:
{
"require": {
"bower-asset/jquery": "1.11.*",
"bower-asset/jquery[2.1.0]": "2.1.0"
}
}
Output:
vendor/bower-asset/jquery/
vendor/bower-asset/jquery-2.1.0-/
That's what the plugin does when there is a dependency that requires several versions. However, it does not operate manually.
In addition to this bug, formatting the output folder is not exemplary (vendor/bower-asset/jquery-2.1.0-
), so I think I'll change the pattern to it become:
{
"require": {
"bower-asset/jquery": "1.11.*",
"bower-asset/jquery-2.1.0": "2.1.0"
}
}
Output:
vendor/bower-asset/jquery/
vendor/bower-asset/jquery-2.1.0/
and update the doc.
from composer-asset-plugin.
Thanks for the quick response!
The current way of working (with the square brackets) is fine for me personally; I was just looking to find the right syntax. But if you change it I'll follow :-)
from composer-asset-plugin.
Fixed by 58aa2d8.
You can find the documentation here.
from composer-asset-plugin.
I was forced to change, because when we add a package manually, the Composer find that the package name was incorrect.
from composer-asset-plugin.
Related Issues (20)
- Asset dependencies not installing from composer.json when no lock file present HOT 6
- git skip update does not work for some repos
- Option to skip update? HOT 2
- Error requiring jquery. HOT 3
- Composer don't install completely all dependencies HOT 5
- Problems installing NPM-assets HOT 16
- Silent removal of dependency during update since Composer 1.6.4 HOT 2
- Request to herokuapp depricated HOT 2
- Composer uses semver. HOT 3
- No valid bower.json was found in any branch or tag of https://github.com/yiisoft/jquery-pjax.git HOT 5
- Composer 1.9.0: "No valid bower.json was found" when referencing a branch of a cloned repository HOT 8
- Compatibility with Composer 2.0 HOT 8
- Compatibility with Composer 2.0 HOT 25
- [npm] fatal: Unable to find remote helper for 'git+https' HOT 3
- request support for composer 2.0 and php8 HOT 2
- composer require npm-asset/xterm-addon-fit fails HOT 1
- PHP8 issue
- Package fxp/composer-asset-plugin at version ~1.3 has a PHP requirement incompatible HOT 2
- Package fxp/composer-asset-plugin has a PHP requirement incompatible with your PHP version HOT 1
- composer global require "fxp/composer-asset-plugin:dev-master" fails HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from composer-asset-plugin.