New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flow kickstart:package does not work on newly created flow distribution #1489

Benjamin-K opened this Issue Jan 2, 2019 · 1 comment


None yet
2 participants
Copy link

Benjamin-K commented Jan 2, 2019


Kickstarting a new package within a new flow project does not work (directly), because the flow package manager looks for the repository keyword in the composer.json, which does not exist. Therefore an error is thrown, when you try to kickstart a new package with flow kickstart:package Acme.Demo.
To fix this, you need to update the composer.json and add the repository key (this should be the case from the beginning!).

Steps to Reproduce

  1. Create a new flow project (composer create-project --keep-vcs neos/flow-base-distribution project-name)
  2. Try to create a new package using the package kickstart command (./flow kickstart:package Acme.Demo
  3. An error will be thrown, showing Warning: Invalid argument supplied for foreach() in .../project-name/Packages/Framework/Neos.Flow/Classes/Package/PackageManager.php line 346

Update your composer.json file, add the repository-keyword and try to run the kickstart-command again and it will work!

Expected behavior

The package can be created without adjusting the composer.json file.

Actual behavior

composer.json needs to be adjusted (repository-key needs to be added`.

Affected Versions

Flow: 5.2.1, didn't test any other version yet.


This comment has been minimized.

Copy link

daniellienert commented Jan 2, 2019

Hey @Benjamin-K,
thanks for reporting.
Should be fixed with the referenced change / next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment