Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The template composer.json defines a direct dependency on several packages that are already dependencies of other packages:
Because these dependencies are effectively defined twice, composer throws a warning when you run composer update on a BLT project:
Right now I think this is a harmless warning, but it could lead to unpredictable behavior if BLT, Drupal console, or Lightning updates or patches one of these dependencies.
Seems like the best solution is to remove them from the project template composer.json, and just allow upstream projects to manage them.