Skip to content

Fixes #14814 Default behavior about unpacking packs by Flex changed #14818

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 11, 2021
Merged

Fixes #14814 Default behavior about unpacking packs by Flex changed #14818

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions setup.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,12 +210,11 @@ For example, to add debugging features in your application, you can run the
which in turn installs several packages like ``symfony/debug-bundle``,
``symfony/monolog-bundle``, ``symfony/var-dumper``, etc.

By default, when installing Symfony packs, your ``composer.json`` file shows the
pack dependency (e.g. ``"symfony/debug-pack": "^1.0"``) instead of the actual
packages installed. To show the packages, add the ``--unpack`` option when
installing a pack (e.g. ``composer require debug --dev --unpack``) or run this
command to unpack the already installed packs: ``composer unpack PACK_NAME``
(e.g. ``composer unpack debug``).
You won't see the `symfony/debug-pack` dependency in your `composer.json`, as Flex
automatically unpacks the pack. This means that it only adds the real packages
as dependencies (e.g. you will see the new `symfony/var-dumper` in `require-dev`).
While it is not recommended, you can use the `composer require --no-unpack ...`
option to disable unpacking.

.. _security-checker:

Expand Down