mozart
mozart copied to clipboard
coenjacobs
Developers tool for WordPress plugins: Wraps all your projects dependencies in your own namespace, in order to prevent conflicts with other plugins loading the same dependencies in different versions.
I'm trying to use this package over php-scoper, as php-scoper is rather complicated and confusing to implement, however, when I try to run `vendor/bin/mozart compose` I keep running into this...
On my project some weird bug happened with prepending same prefix multiple times to classmaps. I couldn't locate where is the problem, so I have prepared "dirty" fix. 
## Problem if you want to use two packages with same namespace (e.g. `illuminate/support` and `illuminate/collections`) which shares similar files, Mozart will throw an "File already exists" error. ## Solution...
While this (https://github.com/coenjacobs/mozart/issues/43) issue was resolved, I found an issue with `aws/aws-sdk-php` not working once Mozart had been run. The Namespace etc. had changed once being ran: ```
I have a WordPress theme which uses Timber via Composer. Timber has a dependency of a version of Twig that has the following autoloader in their composer.json. ``` "autoload": {...
I'm using [Mpdf](https://github.com/mpdf/mpdf) and its namespace and main class name are the same. With: ```json { "require": { "mpdf/mpdf": "8.0.10" }, "minimum-stability": "dev", "require-dev": { "coenjacobs/mozart": "dev-master#3b1243ca8505fa6436569800dc34269178930f39" }, "extra": {...
If the vendor directory is set to anything other than 'vendor', mozart compose fails silently without doing anything. When integrating composer into legacy codebases it is sometimes necessary to use...
Adds support for non-default vendor directory Useful when working on a legacy wordpress theme or plugin where 'vendor' is already in use before adopting composer https://getcomposer.org/doc/06-config.md#vendor-dir
Hello Coen! First of all, great work and thanks for making this tool. Helped me a lot, super easy to use! I learned something when implementing it in my project....
[FPDI](https://www.setasign.com/products/fpdi/about/), whose class extends [FPDF](http://www.fpdf.org/), does not declare the FDPF library as a requirement in its [composer.json](https://github.com/Setasign/FPDI/blob/cddf43dcfe57337bbdc687cb929021174e6696da/composer.json#L17-L20). Its [official documentation](https://manuals.setasign.com/fpdi-manual/v2/installation/#index-2-1) says to require both libraries alongside each other like below....
Metadata
Owner
Metadata
Developers tool for WordPress plugins: Wraps all your projects dependencies in your own namespace, in order to prevent conflicts with other plugins loading the same dependencies in different versions.