Juliette Reinders Folmer

<p>The awesome <a href="https://wordpress.org/plugins/plugin-dependencies/" rel="ugc">WordPress Plugin Dependencies</a> plugin introduces plugin dependency management right into your WordPress admin area.</p>
<p>Unfortunately, the reality is that very few plugins currently contain dependency information and until that changes, the effect of having the WordPress Plugin Dependencies plugin activated is minimal.</p>
<p>This plugin enriches the information about dependencies available to the Plugin Dependencies plugin bridging the gap until plugins catch up and start incorporating the <code>Depends</code> and <code>Provides</code> tags in their file headers properly.</p>
<blockquote>
<p>You’ll need to have version <strong>1.3</strong> or higher of the <a href="https://wordpress.org/plugins/plugin-dependencies/" rel="ugc">WordPress Plugin Dependencies</a> plugin installed for this plugin to have any effect.</p>
</blockquote>
<h4>Disclaimer:</h4>
<p>The dependency list provided by this plugin is – <em>and will always be</em> – incomplete.</p>
<p>Additional information to be added to the list is <a href="https://github.com/jrfnl/wp-known-plugin-dependencies/pulls" rel="nofollow ugc">very welcome</a> and will be gracefully accepted.</p>
<p>Even better: send a pull request or bug report to your favorite add-on plugin requesting them to start using the tags.</p>
<h4>Background</h4>
<p>This plugin was inspired by <a href="https://github.com/x-team/wp-plugin-dependencies/issues/34" rel="nofollow ugc">this discussion</a>.</p>
<p>Rather than having individual developers create their own lists to enrich the available information, this plugin tries to  bundle the knowledge of dependencies.</p>
<p>The ultimate goal is for the <code>Depends</code> tag to be widely adopted and this plugin to become obsolete.</p>
<p>Of course, it would also help <strong>a lot</strong> if the Depends/Provides tags would be officially recognized and mentioned in the <a href="https://wordpress.org/plugins/about/faq/" rel="ugc">Plugin Developers FAQ</a> and if what’s expected to be at the top of the main .php file would be as well documented as the readme.txt file in the <a href="https://wordpress.org/plugins/about/" rel="ugc">Developer Center</a>, but that’s a whole other challenge 😉</p>
<p>Any lobbying you can do for this will of course be encouraged and applauded!</p>
<p>If you like this plugin, please <a href="https://wordpress.org/support/view/plugin-reviews/known-plugin-dependencies" rel="ugc">rate and/or review</a> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the <a href="https://wordpress.org/support/plugin/known-plugin-dependencies" rel="ugc">Support Forum</a> or in the <a href="https://github.com/jrfnl/wp-known-plugin-dependencies/issues" rel="nofollow ugc">GitHub repository</a>.</p>


Known Plugin Dependencies

Add-on plugin for the WordPress Plugin Dependencies plugin, injecting additional information about known dependencies between plugins.

Sean Fisher

<p>Adding Composer dependency management to WP CLI. Allows you to recursivly install/update composer packages inside of all of your WordPress plugins and themes.</p>
<h3>What is this using?</h3>
<p>This package uses a great piece of software called <a href="http://wp-cli.org/" rel="nofollow ugc">WP-CLI</a>. It provides a command line interface for WordPress management. We are a plugin providing Composer management inside of WP CLI.</p>
<h3>What’s Composer?</h3>
<p>It’s the greatest thing to happen to the web since GIFs, Drop Shadows and dancing cats. Composer is a dead simple JSON-based dependency manager for PHP. For more information, check out <a href="http://getcomposer.org/" rel="nofollow ugc">http://getcomposer.org/</a>.</p>
<h3>So this is complete Composer support?</h3>
<p>No, not exactly! Sadly, I’m building this out and I’m trying to make some sweet WP-CLI and Composer integration. But for now, we only support a few command:</p>
<ul>
<li>install</li>
<li>update</li>
<li>diagnose</li>
<li>help</li>
<li>status</li>
</ul>
<p>If you’d love to help out, please help! Make a pull request and let’s get coding!</p>
<h3>How do I build Composer Management inside of my plugin?</h3>
<p>Simple really! You just create a simple <code>composer.json</code> file like you would with any Composer project. From there, wp-composer will interface with each plugin/theme that has composer support and it will generate the autoload files, too!</p>
<p>Just include something like this inside your main plugin file:</p>
<pre><code>require(__DIR__.'/vendor/autoload.php');
</code></pre>
<p>It’s that simple.</p>


WP Composer

Adding Composer dependency management to WP CLI.

Known Plugin Dependencies vs WP Composer