Repository navigation
Conversation
zburke
marked this pull request as ready for review
October 5, 2026 19:03
JohnC-80
approved these changes
Oct 6, 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
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.



Packages pull in
@folio/stripes-webpacktransitively, typically via this package. Thus, the way to supply the updated version of stripes-webpack is to supply a new version of stripes-cli.babelConfig@folio/stripes-webpackto a version that no longer relies onbabelUnrelated, except quite related in the sense of "pruning old stuff that is no longer in use":
@folio/stripes-testingdependency, because nothing has relied on it since the NightmareJS tests were purged from platform-complete years ago and it's hard to believe we didn't think of doing this soonerRefs STCLI-292