Summary

When inline: true is set on the assets loader, inlineAssets builds the list of scales passed to AssetSourceResolver.pickScale from Object.keys(sourceSet). JavaScript lists integer-like keys first, so the scales [0.75, 1, 1.5, 2, 3] come out as [1, 2, 3, 0.75, 1.5]. pickScale assumes ascending order and returns the first scale that is greater than or equal to the device pixel ratio, or the last one if none match. With the unsorted list, an asset that has a fractional variant resolves to the wrong image:

Assets with only integer scales (@1x, @2x, @3x) are not affected.

This change builds the scales from assets, which the loader already sorts in ascending order. The inlined source set itself is unchanged.

Test plan

• New unit test packages/repack/src/loaders/assetsLoader/__tests__/inlineAssets.test.ts evaluates the generated module with the same logic as React Native's pickScale for pixel ratios 0.75, 1, 1.5, 2.625 and 3.5.
  • Without the fix: 3 failed, 2 passed.
  • With the fix: 5 passed.
• pnpm --filter @callstack/repack test: 42 suites, 364 tests passed.
• pnpm vitest run src/loaders/assets-loader.test.ts in tests/integration: 76 passed, existing snapshots unchanged.
• pnpm --filter @callstack/repack typecheck and biome check pass.
• Added a patch changeset for @callstack/repack.

Fixes #1504