composer without continuous integration

then odds are you're left with crucial step of figuring out how to manage the directory when deploying your plugins...   We know it's idea to throw the directory under source control, Other developers.   You're not checking the directory into the repository, except you're also not using integration to deploy the plugin.   Export the branch from your local copy of the plugin, then make sure you run the Composer command that instructs it to create the directory without the development-level dependencies..   First, I'm assuming that the local copy of your plugin does not have copy of the directory except has all of the latest code pulled from the remote repository..   That is, you have the latest, version of code ready to be released and you're not yet ready to do say, autoloading and other similar functionality..   Next, instruct Composer to install the dependencies that are outside of the require-dev in your composer json file.   I would not say this is ideal except it's solution to use case that certainly exists, so I'd say that it's something that can be done to solve specific problem..   Ultimately, if you're looking for way to distribute WordPress plugin that uses Composer without integration, this is way to do it..   I recognize, it's specific use case and thus has specific solution..   Read more