Repository navigation
fix: preserve browser targets and transforms in utoopack builds - #873
Draft
fireairforce wants to merge 2 commits into
Draft
fireairforce wants to merge 2 commits into
fireairforce wants to merge 2 commits into
Conversation
This was referenced Oct 13, 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.
Browser UMD builds with utoopack dropped Father browser targets and configured transforms, and could change JSX import sources.
Forward targets and supported Emotion settings, apply dependency Emotion transforms in Father, and validate native decorator metadata flags. Preserve native Emotion JSX inference and explicit user overrides; keep Webpack's existing path.
Validation: TypeScript build/type check, 3 Jest suites (44 tests), and formatting checks. Keep this draft until the Pack fixes are released and its dependency can be updated.