Repository navigation
chore: replace vendored i18n and UI with npm beta.147 - #42
Merged
Merged
Conversation
callumalpass
marked this pull request as ready for review
October 29, 2026 20:38
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.
Summary
Compatibility
Verified both exact versions with npm view. Unpacked npm-vs-vendored comparisons differ only in package.json version metadata (and the UI kit devDependency version). All runtime code, declarations, stylesheets, catalogues and CLI files are byte-identical, so no API/visual adaptation is necessary. Existing real-runtime backslash/double-encoding regressions pass without an app-side wrapper.
Validation
No publication, release, deployment or dispatch. Awaiting GitHub CI (including full Chromium baseline/reliability/i18n/accessibility/editing/feedback coverage) before authorized merge.