The installer dependency gets included too late for 2.4,
so framework ends up in the wrong path. That's a bug with composer,
see See https://github.com/composer/composer/issues/1147
Until its fixed, we remove the explicit dependency which seems
to trigger this path in the dependency resolver (works for 3.x)
Moved to end of requirements, to work around a bug in composer - see https://github.com/composer/composer/issues/1147. This caused the dependencies to be installed in the wrong folder because the custom 'silverstripe-module' instructions hadn't been loaded at the time the core modules were installed via composer.
Moved to end of requirements, to work around a bug in composer - see https://github.com/composer/composer/issues/1147. This caused the dependencies to be installed in the wrong folder because the custom 'silverstripe-module' instructions hadn't been loaded at the time the core modules were installed via composer.
