Repository navigation
chore(deps): bump @utoo/pack to v1.5.27 - #874
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Bump the pinned
@utoo/packdependency from1.5.26to1.5.27, keeping the shared and native platform packages aligned in the pnpm lockfile. This brings in the upstream fix that keeps initial and dynamically imported library CSS in a single output chunk, plus dev server and native subscription cleanup improvements.Validation on macOS with Node.js 22:
pnpm install --frozen-lockfilepnpm run buildpnpm exec tsc --noEmitpnpm --dir boilerplate run buildCI=true NODE_ENV=test pnpm exec jest --runInBand --silent --runTestsByPath tests/utoo-pack.config.test.ts tests/utoo-pack.build.test.ts(34 tests)CI=true NODE_ENV=test pnpm exec jest --runInBand --silent --forceExit --testPathIgnorePatterns=tests/utoo-pack.build.test.ts(16 suites / 151 tests)pnpm --dir examples/utoo-pack run buildAll 17 suites / 183 distinct tests passed across the two test invocations. The utoopack build suite runs in a separate process because both build suites register the native worker pool, which conflicts with Jest's suite isolation under
--runInBand. The remaining suites use--forceExitfor the existing open handles after testing.