Magento Marketplace is going through beta testing before opening up more widely. One area that has become clear is the need for a tool to help with verifying the packaging of extensions before submission. This blog post is a preview into this tool so extension developers can try it out today and provide feedback.
In doing submission walk-throughs with a number of application developers, a common source of friction was getting the ZIP upload “just right”. There is the composer.json file, the overall structure of the ZIP file, etc. Because Composer is a new approach for Magento and it was the first time for many extension developers building a Composer ZIP, there were a few repeating problems that came up. The issues were simple to fix, but wasted time during the submission process. So, we are making a tool available that extension developers can use to detect common problems before they attempt to submit. We are making a beta of this script available now to collect feedback before official release.
The script is currently available as a GIST. [Update Feb 19: V2 now available here.] (This may be taken down in the future when the official release is made.) The current version is a standalone PHP script that takes the Composer package ZIP file(s) on the command line. Errors are reported to the screen. Examples include a missing composer.json file, missing fields in the composer.json file, and so on.
$ php validate_m2_package.php my-theme.zip my-module.zip
Please leave any issues you encounter in the comments section below. Examples of problems include false positives (reported errors that are not really errors) and false negatives (missed problems).