STRWEB-159: @module-federation/enhanced ^2.8.1 removing axios - #191
Merged
Conversation
… removing axios https://folio-org.atlassian.net/browse/STRWEB-159 Upgrade @module-federation/enhanced from ^2.0.0 to ^2.8.1 in package.json. stripes-webpack’s yarn.lock has this axios dependency path: * @module-federation/enhanced@2.3.1 › @module-federation/cli@2.3.1 › @module-federation/dts-plugin@2.3.1 › axios@1.13.5 In recent @module-federation/enhanced versions the axios dependency has been completely removed: module-federation/core#4644 There are multiple known security vulnerabilities in axios@1.13.5 – 3 severe, 7 high, 21 medium: https://security.snyk.io/package/npm/axios/1.13.5 After the change in stripes-webpack’s package.json has been made and some other module bumps the stripes-webpack version then yarn will automatically remove this axios dependency from the other module’s yarn.lock file. This helps the FOLIO Security Team triaging whether FOLIO is affected by axios security vulnerabilities, and gives implementers more confidence that FOLIO is secure. The snapshot reference environments run with @module-federation/enhanced@2.8.1: https://github.com/folio-org/platform-lsp/blob/snapshot/yarn.lock To keep stripes-webpack developer environments in sync with the snapshot reference environments we should update stripes-webpack’s yarn.lock file from time to time.
|
zburke
approved these changes
Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://folio-org.atlassian.net/browse/STRWEB-159
Upgrade @module-federation/enhanced from ^2.0.0 to ^2.8.1 in package.json.
stripes-webpack’s yarn.lock has this axios dependency path:
In recent @module-federation/enhanced versions the axios dependency has been completely removed: module-federation/core#4644
There are multiple known security vulnerabilities in axios@1.13.5 – 3 severe, 7 high, 21 medium: https://security.snyk.io/package/npm/axios/1.13.5
After the change in stripes-webpack’s package.json has been made and some other module bumps the stripes-webpack version then yarn will automatically remove this axios dependency from the other module’s yarn.lock file.
This helps the FOLIO Security Team triaging whether FOLIO is affected by axios security vulnerabilities, and gives implementers more confidence that FOLIO is secure.
The snapshot reference environments run with @module-federation/enhanced@2.8.1: https://github.com/folio-org/platform-lsp/blob/snapshot/yarn.lock
To keep stripes-webpack developer environments in sync with the snapshot reference environments we should update stripes-webpack’s yarn.lock file from time to time.