!!! TASK: Make composer autoloader the default

[albe]

The old behaviour can now still be achieved by setting FLOW_ONLY_COMPOSER_LOADER=false, but is (still) deprecated and will be gone at some point.

This is a breaking change if you relied on the old behavior, specifically on the fact that Flow used to consider all packages underneath the /Packages folder.

From now on, packages will only be loaded if they are properly installed via composer!

Related to #2262

[bwaidelich]

Nice one, thanks for taking care.

I can't really judge if our custom ClassLoader can be disabled without further side effects. Probably @kitsunet can tell that. Or we just test it :)

[bwaidelich]

If we agree to this, we should also update the docs (see #2280 (comment))

[bwaidelich]

+1 by reading (and Neos demo seems to work with it) but I would like another opinion on that since I never really understood the differences of our own ClassLoader tbh

[bwaidelich]

Note: I just realized that ./flow kickstart:site (and probably also ./flow kickstart:package) doesn't actually add the new package to the composer manifest (see neos/neos-development-collection#3217). I could imagine that this will break without our own ClassLoader, right?

[albe]

Good point. That's definitely something to check.

[kdambekalns]

I could imagine that this will break without our own ClassLoader, right?

That is fixed by now (see neos/neos-development-distribution#59)

[kdambekalns]

Fine with me.

[albe]

🤞