Last activity 21 Apr 2024 134 154 156998
composer require neos/flow-development-collection

Flow packages in a joined repository for pull requests.


Release Date
Feb 23, 2024 16:38
Requires (dev)
  • ext-memcache: If you have a memcache server and want to use it for caching.
  • ext-memcached: Alternative, if you have a memcache server and want to use it for caching.
  • ext-redis: If you have a redis server and want to use it for caching.
  • ext-igbinary: The igbinary extension is a replacement for the standard PHP serializer
  • ext-curl: To use the \Neos\Flow\Http\Client\CurlEngine
  • doctrine/data-fixtures: To manage and execute the loading of data fixtures for the Doctrine ORM or ODM
  • neos/party: To make use of basic user handling
  • php-uuid: For fast generation of UUIDs used in the persistence.
  • neos/fluid-adaptor: For rendering templates with TYPO3.Fluid
MIT 43a130c4e54d43d154a7fd7d0583a02e589ab649

Travis Code Climate StyleCI Latest Stable Version commits since latest release License Documentation API Docs Slack Discussion Forum Issues open issues issue resolution Translation Twitter

Flow development collection

This repository is a collection of packages for the Flow framework (learn more on The repository is used for development and all pull requests should go into it.

If you want to use the Flow framework, please have a look at the documentation:


If you want to contribute to Flow Framework and want to set up a development environment, then follow these steps:

composer create-project neos/flow-development-distribution flow-development dev-master --keep-vcs

Note the -distribution package you create a project from, instead of just checking out this repository.

The code of the framework can then be found inside Packages/Framework, which itself is the flow-development-collection Git repository (due to the --keep-vcs option above). You commit changes and create pull requests from this repository. To commit changes to the framework switch into the Framework directory (cd Packages/Framework) and do all Git-related work (git add ., git commit, etc) there.

In the root directory of the development distribution, you can do the following things:

To run tests, run ./bin/phpunit -c ./Build/BuildEssentials/PhpUnit/UnitTests.xml for unit or ./bin/phpunit -c ./Build/BuildEssentials/PhpUnit/FunctionalTests.xml for functional/integration tests. If you are on 6.0 or later, you can also run ./bin/psalm --config=Packages/Framework/psalm.xml to run static analysis tools.

To switch the branch you intend to work on: git checkout 5.3 && composer update


We use an upmerging strategy, so create all bugfixes to lowest maintained branch that contains the issue (typically the second last LTS release, which is 5.3 currently), or master for new features.

For more detailed information, see and

The content of the readme is provided by Github
The same vendor provides 93 package(s).