Document dependencies

In order to make it easy for non developers to study the dependencies of the PrestaShop open source software, the Devdocs must include a tree of the dependencies, for the core and the native modules.

This must include:

• Integrated dependencies in the repositories
• Composer managed dependencies
• NPM managed dependencies
• The dependencies of the dependencies
• And in general, all third party code and libraries used in the project.

A difference must be made between:

• The dependencies that are built and redistributed in the PrestaShop installer of a release (the zip file)
• The dependencies used only for development purpose and that are not included in the build

There are two aims:

• Study and identify dependencies that are not compatible with the OSL license for redistribution
• Generate comprehensive "third party licenses" files with lists and licences of all the dependencies in the project builds (core and native modules)

In general, please note that the PrestaShop open source project is distributed under the OSL license. It means that in the build/release, only third party code and libraries distributed under the compatible licenses must be used:

• MIT
• BSD
• EUPL
• AFL
• OSL

"Development only" dependencies are not built and distributed in the software, so this license restriction does not apply.

Start with the Devdocs, the core and native modules, and the release installer zip to map which dependencies are built and redistributed. Review the Composer- and NPM-managed dependencies, including transitive dependencies, and compare development-only dependencies with release contents. Done means the dependency tree and comprehensive third-party license files distinguish redistributed code from development-only code.