Closed TMFHokies closed 1 year ago
At present, this is the expected behavior. Thank you.
Thanks for the response!
At present, this is the expected behavior. Thank you.
Would you mind helping me understand why?
Thanks for the response!
At present, this is the expected behavior. Thank you.
Would you mind helping me understand why?
@kayw-geek Sorry to bring up an old thread, but did you happen to see the question above?
Thanks for a great tool!
Thanks for the response!
At present, this is the expected behavior. Thank you.
Would you mind helping me understand why?
@kayw-geek Sorry to bring up an old thread, but did you happen to see the question above?
Thanks for a great tool!
Sorry, I don't know the reason, That may be for the author to answer.
Hi all,
My team is adopting
monorepo-builder
to merge manyrepos into a monorepo. However, I noticed thatmonorepo-builder merge
does not remove unused packages from the main composer.json. So consider this scenario, there are two packages —monorepo/a
andmonorepo/b
— in the monorepo. Onlymonorepo/a
specifiesmonolog/monolog
. Then I run:However, after those commands
monolog/monolog
still exists in the main composer.json but notpackages/a/composer.json
.Do I have the workflow wrong, or is this intended behavior?
Thanks for your help!