@xtreamwayz —

In flat mode only I get this: Cannot read config from App\ConfigProvider - class cannot be loaded. This is only in flat mode (minimal and modular works as expected). It goes wrong when composer executes post-create-project-cmd: @development-enable in flat mode. After running composer update the composer development-enable is working.

Ugh, this may be a chicken-egg problem. We have an autoloader setup by default for the modular structure currently, and then, during install, rewrite it to the flat structure.

What I'm thinking is that we may need to enable the App module during installation, instead of having it enabled in the configuration by default; that would allow development mode to trigger immediately. I'll give that a try today.

mikey179/vfsstream is installed while it's not in composer.json ??? AFAIK dev dependencies of included packages are not installed. Yet it is installed. We have had this a long time ago but I fixed that by updating the stability flags.

I noticed this as well when running create-project — you'll note that you get prompted to install the config providers for zend-validator and one other ZF component when installing, and these are both only because the components are in the original require-dev section, prior to rewriting. So it's not isolated to vfsStream.

That said, I'll still see about rewriting the CopyFileTest to remove that dependency; shouldn't be hard.

In ExpressiveInstallerTest\InstallerTestCase the line use org\bovigo\vfs\vfsStream; can be removed as it's not used.

Will make that change today.

Thanks for all the feedback!

A fix for the post-create-project-cmd: @development-enable execution issue:

Change (towards the end of OptionalPackages::install):

    // Set required packages
    $rootPackage->setRequires(self::$composerRequires);
    $rootPackage->setDevRequires(self::$composerDevRequires);

    // Set stability flags
    $rootPackage->setStabilityFlags(self::$stabilityFlags);

with:

    // Update root package
    $rootPackage->setRequires(self::$composerRequires);
    $rootPackage->setDevRequires(self::$composerDevRequires);
    $rootPackage->setStabilityFlags(self::$stabilityFlags);
    $rootPackage->setAutoload(self::$composerDefinition['autoload']);
    $rootPackage->setDevAutoload(self::$composerDefinition['autoload-dev']);

Second fix:

Turns out removing dependencies are case sensitive! Change 'mikey179/vfsStream' to 'mikey179/vfsstream' in the OptionalPackages::$devDependencies array.

I noticed this as well when running create-project — you'll note that you get prompted to install the config providers for zend-validator and one other ZF component when installing, and these are both only because the components are in the original require-dev section, prior to rewriting.

No, they are requirements for zend-expressive-zendrouter:

 zendframework/zend-expressive-zendrouter 2.0.0
 ├──zendframework/zend-expressive-router ^2.0
 ├──zendframework/zend-psr7bridge ^0.2.2
 │  └──zendframework/zend-http ^2.5
 │     ├──zendframework/zend-uri ^2.5
 │     │  └──zendframework/zend-validator ^2.5
 │     └──zendframework/zend-validator ^2.5
 └──zendframework/zend-router ^3.0
    ├──zendframework/zend-http ^2.5
    │  ├──zendframework/zend-uri ^2.5
    │  │  └──zendframework/zend-validator ^2.5
    │  └──zendframework/zend-validator ^2.5

As said on IRC, the prompt is only there if you select zend-expressive-zendrouter as the router. All other packages don't trigger installation of those packages or that prompt.

A fix for the post-create-project-cmd: @development-enable execution issue:

Thanks - made those changes (and the others you suggested) and pushed. Working on the other feedback now.

That said, I'll still see about rewriting the CopyFileTest to remove that dependency; shouldn't be hard.

Actually, on review of this test case, a mock filesystem is a better plan. Mocking didn't work with the other tests, as they needed to aggregate the configuration, which did not work with vfsStream due to inability to work with glob(). CopyFileTest does not require that.