WP Manifestindependent plugin directory
manifest / developer / composerpress

Composerpress

Takes stock of a local install and generates a composer.json

by Tom J Nowell · github.com/tomjn/composerpress · website

★ 87stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/tomjn/composerpress/archive/refs/heads/master.zip

On Packagist as tomjn/composerpress:

composer require tomjn/composerpress
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Readme github.com/tomjn/composerpress ↗

Retroactively attempts to create a composer.json for a WordPress site. On activation, a composer.json menu appears in the admin area under the Tools menu. This page shows what composerpress thinks a composer.json that will generate a website close or identical to the site the plugin is installed on might look like.

Includes support for detecting/reverse engineering composer packages via:

Installation Notes

Install as a regular plugin and then run composer install on the wp-content/plugins/composerpress plugin folder to install dependencies.

For instructions on installing composer: see here for *nix and here for Windows

TODOs:

Currently ComposerPress does not perform any checking with wpackagist #2 (or similaries), leaving open these problems:

  • when a TextDomain doesn't match a Plugins Name ?
  • when a plugin doesn't match its Folder Name ?
  • when a Plugin is Custom to a site (ie doesn't exist in the wp.org repo)?

Keep in mind

  1. At present, if composerpress can not find the source of a plugin, the choice will fall back on the default "composerpress" (to help you recognize them and act accordingly)

  2. If you encounter a false positive try to contact plugin's author and ask them to insert, at least a Plugin URI: in the header of the plugin; for example: these two plugins could collide if a URI plugin was not specified:

  • Plugin URI: http://wordpress.org/extend/plugins/wp-less/ that will become something like wpackagist-plugin/wp-less
  • Plugin URI: https://github.com/sanchothefat/wp-less/ that will become something like sanchothefat/wp-less
  1. You can always give an help and contribute... :smile:

Author articles