Comments (4)
Yeah like you say the current system ensures every project is in control of that, and that does have drawbacks for sure, but at least it gives you control so you don't get stuck.
from installers.
Yes.. if you don't want your package to be treated special, don't use a type that is typically associated and handled specially by composer/installer?
from installers.
The problem is not my package, the problem is the package I don't have control of 🙈
That package (which is my requirement) has a type of wordpress-dropin
. I mean, I did manage to solve this issue (I have a command that can delete it manually), but I thought that there is a way to prevent this from happening automatically?
I can see the problem with this approach because if my package could do this, and is a dependency it could overwrite the intended behavior of other packages :S
from installers.
Ok, I mean it's a minimal annoyance at best, I managed to find the solution, so it's ok.
And I get that it could potentially cause more issues than it solved 👍🏼
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
- 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 HOT 1
- 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 HOT 1
- Composer Install Installs Modules in "vendor" Instead of Specified "modules" Directory 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 installers.