-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): bump @metamask/eth-trezor-keyring
to ^6.0.0
#27689
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/[email protected] |
Quality Gate passedIssues Measures |
^4.0.0
^6.0.0
package.json
Outdated
@@ -251,7 +251,8 @@ | |||
"@ledgerhq/hw-app-eth@npm:^6.39.0": "patch:@ledgerhq/hw-app-eth@npm%3A6.39.0#~/.yarn/patches/@ledgerhq-hw-app-eth-npm-6.39.0-866309bbbe.patch", | |||
"@ledgerhq/evm-tools@npm:^1.2.3": "patch:@ledgerhq/evm-tools@npm%3A1.2.3#~/.yarn/patches/@ledgerhq-evm-tools-npm-1.2.3-414f44baa9.patch", | |||
"cross-spawn@npm:^5.0.1": "^7.0.6", | |||
"@solana/web3.js@npm:^1.95.0": "^1.95.8" | |||
"@solana/web3.js@npm:^1.95.0": "^1.95.8", | |||
"tslib": "~2.6.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this tslib
forced resolution has been added to fix this error that prevents the wallet unlock:
TypeError#1: Cannot assign to read only property 'Symbol(Symbol.iterator)' of object '[object Object]'
(anonymous) @ sentry-install.js:37776
sentry-install.js:37776 at Object.__generator (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-8.js:49554:131)
at Mutex.<anonymous> (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-5.js:22679:28)
at chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-8.js:49548:41
at new Promise (<anonymous>)
at Object.__awaiter (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-8.js:49544:16)
at Mutex.acquire (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-5.js:22676:24)
at CurrencyRateController.updateExchangeRate (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-1.js:21928:42)
at CurrencyRateController._executePoll (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-1.js:21994:16)
at chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/common-1.js:24712:24
at sentryWrapped (chrome-extension://bclblcklhpbhilglihnehjhmpfchmmpp/scripts/sentry-install.js:21642:17)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two suggestions: Could we drop tslib
as a top-level dependency, and can we narrow this resolution further?
The resolution is currently applied to all copies of tslib
in the dependency tree, not just the one that was causing an issue here. Some of the affected versions are asking for a range that doesn't include 2.6 (e.g. there was on 1.x copy)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The direct dependency has been added because it is a peer dependency of @trezor/connect-web
, which is a dependency of both the keyring and the client (because of the offscreen client-defined keyring). I suppose that some other package already provided it, but I thought it would be good to add it explicitly. Do you think we should remove it?
Regarding the resolution, it is indeed too broad, and we are getting rid of 1.x - I'll try to narrow it down
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On a sidenote, I believe we have wrongly added a "direct" dep to tslib
on Trezor keyring here:
We probably should have use a peer dep for this one instead... I'll check/track this internally to avoid having this resolution (cause I do believe we could get rid of it if we the dependency was done correctly on our side)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this issue is due to a specific version range of tslib
which is incompatible with certain parts of the extension, so we probably would have experienced it regardless at some point
^6.0.0
@metamask/eth-trezor-keyring
to ^6.0.0
Builds ready [458e0a1]
Page Load Metrics (1992 ± 88 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
@metamaskbot update-policies |
No policy changes |
Builds ready [06a0b65]
Page Load Metrics (1593 ± 83 ms)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I rely on e2e tests for validation though.
Builds ready [37aed22]
Page Load Metrics (1614 ± 132 ms)
|
Good to me. Tested locally and was able to test successfully (with Trezor simulator) the provided scenario:
|
Description
This PR bumps
@metamask/eth-trezor-keyring
from^3.1.3
to^6.0.0
.Related issues
Fixes:
Manual testing steps
These changes directly impact Trezor devices:
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist