I'm using some composer packages (like microsoft/application-insights) in the extension I've developed and now that I'm trying to submit the extension for technical review I've got a lot of errors for the files from the vendor folder. Is there some documentation about how to approach these cases? I've seen something about shared packages, but I don't think this is my case.

Anyone else has some experience with external packages in your extension? Thanks


That sounds like you are submitting the extension with its own vendor directory. If the external dependencies are publicly available, just include them as requirements in composer.json. Do not submit vendor and composer.lock to the marketplace.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.