Development Installs

During package development, install the package into a QUIQQER system through Composer so the runtime sees the same package metadata, autoloading, XML files, and Composer events as a normal installation.

Use the installation root for these commands.

Install A Package From A Git Repository

Add the package repository to the installation root composer.json.

{
  "repositories": [
    {
      "type": "vcs",
      "url": "git@dev.example.com:vendor/package.git"
    }
  ]
}

Then require the package through the QUIQQER console:

./console composer require vendor/package:dev-main

Use the branch name that matches the repository. Composer branch constraints use the dev- prefix, for example dev-main, dev-next-2.x, or dev-feature/example.

QUIQQER's Composer integration runs the registered package events for install and update operations. Watch the command output for setup or dependency errors.

Work On A Package In Source Form

For active development, prefer a source checkout over a downloaded archive. Development installations can set Composer's preferred install mode to source.

./console composer config preferred-install source
./console composer update vendor/package

If the package is already installed from a dist archive, remove and require it again after adding the VCS repository.

Install An Unstable Version

Require explicit development versions when testing a branch:

./console composer require vendor/package:dev-next-2.x

If Composer refuses the version because of stability settings, allow development versions in the installation root:

./console composer config minimum-stability dev
./console composer config prefer-stable true

Use explicit version constraints for the package you are testing. Do not leave a production system on broad development constraints unless that is intentional.

Path Repositories

For local package work, a Composer path repository can point to a checkout on the same machine.

{
  "repositories": [
    {
      "type": "path",
      "url": "../packages/vendor/package",
      "options": {
        "symlink": true
      }
    }
  ]
}

Then require the package with a matching version constraint:

./console composer require vendor/package:dev-main

Path repositories are useful for local development. Do not use machine-local paths in shared production configuration.

Practical Checklist

Before installing development versions:

• Add a vcs or path repository in the installation root.
• Require the exact development branch with a dev- constraint.
• Keep prefer-stable enabled when broader dev stability is needed.
• Verify the package installed as source when you need to edit it.
• Avoid committing local path repositories into shared installation configuration.