Is your feature request related to a problem? Please describe.
For the dev environments, it is usually enough to fetch the vendor files once, which do not change very often. We already have them on the disk if there was no change in composer.json, it is not necessary to refetch them.
Another example is, that maybe I want to experiment with something locally, so I install some extra libraries, and later upon new dekick local everything disappears.
Describe the solution you'd like
Dekick asks a question whether we would like to run seeders. Maybe it could be done similarly? We would need an option for the command line as well where we could start dekick with forcing or not composer install. And maybe an option in a config file, where we could specify, that for this project we don't want to refetch vendor files.
Is your feature request related to a problem? Please describe.
For the dev environments, it is usually enough to fetch the vendor files once, which do not change very often. We already have them on the disk if there was no change in composer.json, it is not necessary to refetch them.
Another example is, that maybe I want to experiment with something locally, so I install some extra libraries, and later upon new
dekick localeverything disappears.Describe the solution you'd like
Dekick asks a question whether we would like to run seeders. Maybe it could be done similarly? We would need an option for the command line as well where we could start dekick with forcing or not
composer install. And maybe an option in a config file, where we could specify, that for this project we don't want to refetch vendor files.