chore: Remove outdated replace and extra definitions from composer files
#181
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.
Based on the discussions in magento/magento2#36543 and magento/magento2#34562, this removes all composer
replaceandextrareferences to these packages:These modules all are (or were at some time in the past) integrated into the Magento 2 core codebase. These rules were added to prevent the (mostly JS/frontend) components from being included separately, which would result in duplicate code in an installation.
However:
roave/security-advisoriesalerts, which is now audited by default as of Composer 2.9. (See Composer update failing because of security advisory #178)Removing all references in this way should fix the audit error for Composer 2.9, and clean up in the process.
Tangentially related PR: mage-os/mageos-magento2-page-builder#9