chore: bump react-native-ble-plx 3.2.1 β 3.4.0#7323
chore: bump react-native-ble-plx 3.2.1 β 3.4.0#7323janicduplessis merged 3 commits intodevelopfrom
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
π§ͺ Flashlight Performance Report (AWS Device Farm) π Commit: c4e37ef π View Artifacts
|
b6ab841 to
e8f17d4
Compare
|
@janicduplessis robot Ole is not happy. Can we check if this is true?
|
20b21bc to
70264c8
Compare
e99723e to
0fd40ed
Compare
Also bumps @ledgerhq/react-native-hw-transport-ble 6.33.4 β 6.34.1 so both depend on the same ble-plx version (3.4.0), avoiding a native/JS argument mismatch crash on Android introduced in ble-plx 3.5.0. ble-plx 3.4.0 dropped its expo/config-plugins dependency, cleaning up ~120 transitive babel packages from the lockfile.
0fd40ed to
148e584
Compare
olerass
left a comment
There was a problem hiding this comment.
LGTM with the companion bump π
Adds an explicit yarn resolution for @ledgerhq/logs. Without this, yarn can end up with multiple versions of @ledgerhq/logs hoisted into node_modules when dependencies are updated (different ledgerhq packages specify different semver ranges), which produces two separate LocalTracer class definitions with incompatible private fields and breaks src/utils/ledger.ts under tsc. This should have been added alongside the ble-plx / hw-transport-ble bump in #7323 β the next dep bump that touches anything ledgerhq-adjacent will re-introduce the duplicate otherwise.
Adds an explicit yarn resolution for @ledgerhq/logs. Without this, yarn can end up with multiple versions of @ledgerhq/logs hoisted into node_modules when dependencies are updated (different ledgerhq packages specify different semver ranges), which produces two separate LocalTracer class definitions with incompatible private fields and breaks src/utils/ledger.ts under tsc. This should have been added alongside the ble-plx / hw-transport-ble bump in #7323 β the next dep bump that touches anything ledgerhq-adjacent will re-introduce the duplicate otherwise.
Adds an explicit yarn resolution for @ledgerhq/logs. Without this, yarn can end up with multiple versions of @ledgerhq/logs hoisted into node_modules when dependencies are updated (different ledgerhq packages specify different semver ranges), which produces two separate LocalTracer class definitions with incompatible private fields and breaks src/utils/ledger.ts under tsc. This should have been added alongside the ble-plx / hw-transport-ble bump in #7323 β the next dep bump that touches anything ledgerhq-adjacent will re-introduce the duplicate otherwise.
Adds an explicit yarn resolution for @ledgerhq/logs. Without this, yarn can end up with multiple versions of @ledgerhq/logs hoisted into node_modules when dependencies are updated (different ledgerhq packages specify different semver ranges), which produces two separate LocalTracer class definitions with incompatible private fields and breaks src/utils/ledger.ts under tsc. This should have been added alongside the ble-plx / hw-transport-ble bump in #7323 β the next dep bump that touches anything ledgerhq-adjacent will re-introduce the duplicate otherwise.
Fixes APP-3610
What changed (plus any additional context for devs)
Bumps
react-native-ble-plxfrom 3.2.1 to 3.4.0 and@ledgerhq/react-native-hw-transport-blefrom 6.33.4 to 6.34.1.Key changes in ble-plx 3.3β3.4:
BleManageris now a singleton (safe to declare in React tree)expo/@expo/config-pluginsdirect dependencies, cleaning up ~120 transitive babel packages from the lockfileWe bump to 3.4.0 instead of 3.5.x because 3.5.0 added a
subscriptionTypeparameter tomonitorCharacteristic*native bridge methods on Android (4 β 5 args). The Ledger transport's JS still calls with 4 args, causing aNativeArgumentsParseExceptioncrash. By using 3.4.0 β which Ledger transport 6.34.1 also depends on β both JS and native stay aligned with no resolution needed.Extracted from the RN 0.81 upgrade PR #6924.
Screen recordings / screenshots
N/A
What to test