Comments (6)
I believe that is what the vendor-dir
config option is for: https://getcomposer.org/doc/04-schema.md#config
from installers.
vendor-dir
doesn't help at all, installer (v1.0.15) places files in root
from installers.
@Mihailoff Could you post the composer.json you're trying?
from installers.
{
"repositories": [
{ "type": "git", "url": "https://github.com/Mihailoff/installer-test.git" }
],
"require": {
"mihailoff/installer-test": "0.1.0"
},
"config": {
"vendor-dir": "custom"
}
}
from installers.
Ah you're right @Mihailoff. I created an issue for it here: #164 Patches welcome! Thanks!
from installers.
Great! BTW #146 won't solve the initial topic issue. My use case require custom installation path for packages with installer type only. It is again related with location of main framework. It's not important where the vendors directory located. Right now the only way is to repeat in installer-paths all needed types with some prefix.
I really like this idea
{
"extra": {
"installer-paths-prefix": {
"framework-folder": ["framework:wordpress"]
}
}
}
so that wordpress-* types would be automatically install in that path.
from installers.
Related Issues (20)
- When target location change, data must be moved (not duplicated) HOT 3
- Path issue shows with composer installing via MAMP on macOS HOT 1
- Your app key is missing message issue
- Want to write a custom path for plug-in package? I don't know how to debug
- composer 2.3.5 breaks composer/installers HOT 3
- Disabling installer in my package will still trigger the installer path when it's pulled in a project HOT 4
- Add license to the package HOT 1
- Add version to installer-path variables HOT 1
- Add Support for "Generic" Library HOT 2
- Support https://asset-packagist.org/ types? HOT 3
- Using vcs repo without composer.json
- Add a installer for Laminas project
- Renaming vendor breaks composer install HOT 2
- mediawiki-skin should install in CamelCase name directory
- Could we add support of wordpress-core type?
- Why are dependencies still present in the installer path after removal?
- Add support for Moodle "tiny" plugins HOT 1
- Extend documentation regarding disabling of installers
- Add partial support for the generic "library" and "project" types
- Composer Install Installs Modules in "vendor" Instead of Specified "modules" Directory
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 installers.