Disabling installer in my package will still trigger the installer path when it's pulled in a project about installers HOT 4 CLOSED

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.