Skip to content

Commit 5e74358

Browse files
authored
Fixes #14814 Default behavior about unpacking packs by Flex changed
`symfony/flex` since `1.9.0` unpack packs by default (PR symfony/flex#656)
1 parent 9f6437b commit 5e74358

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

setup.rst

+5-6
Original file line numberDiff line numberDiff line change
@@ -210,12 +210,11 @@ For example, to add debugging features in your application, you can run the
210210
which in turn installs several packages like ``symfony/debug-bundle``,
211211
``symfony/monolog-bundle``, ``symfony/var-dumper``, etc.
212212

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

220219
.. _security-checker:
221220

0 commit comments

Comments
 (0)