Module:Update clean up main app composer #1621
Unanswered
ash-g-1337
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Somewhat new to laravel modules, but a question around Module:update -- maybe a feature/gap.
When we call module:update "module" command, it syncs the composer.json (from my understanding, that is what the update command does) with the main app composer. But is there a way to clean up the main app composer if a package is removed from the module.
simplified example.
Main App packages:
"laravel/framework": "^10.10",
"laravel/sanctum": "^3.2",
Module Packages:
"guzzlehttp/guzzle": "^7.2",
"laravel/tinker": "^2.8",
Main App Packages after update
"laravel/framework": "^10.10",
"laravel/sanctum": "^3.2",
"guzzlehttp/guzzle": "^7.2",
"laravel/tinker": "^2.8",
for whatever the reason, we decide to remove guzzle from the module.
When we do update, the ideal main app packages would look like:
"laravel/framework": "^10.10",
"laravel/sanctum": "^3.2",
"laravel/tinker": "^2.8",
is there a way to do this kind of cleanup..
Beta Was this translation helpful? Give feedback.
All reactions