-
Notifications
You must be signed in to change notification settings - Fork 342
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
[Bug]: Incompatible with @ledgerhq/errors #6882
Comments
Any ETA for this issue. |
It would be great to fix this issue until this weekend. |
You could temporarily solve it by adding this in line 91 export const
TransportRaceCondition = createCustomErrorClass("TransportRaceCondition");
in the index.js found at node_modules/ledgerhq/errors/lib-es/index.js
Builds out of your dev environments will not work because the packages will
be restored from public repos. Another solution you can try is to create
your local repository and point your restore endpoint to it. Just make sure
you apply this change in your local repo, and later, when the issue is
fixed, update your local repos with the public.
I know you did not ask but for other people out there.
…On Tue, May 21, 2024 at 2:07 PM josephchung796 ***@***.***> wrote:
It would be great to fix this issue until this weekend.
—
Reply to this email directly, view it on GitHub
<#6882 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACC4WARLBXWRZ7HTORFKAFDZDOEOTAVCNFSM6AAAAABH6QYT4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTGE3DONBQHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Ok, thanks for your help, @coredomain |
Once this issue is permanently fixed in public repo, please let me know. |
@aussedatlo fyi it may relates to your changes in #6394 , i just don't understand how it's possible that hw-transport is published but not errors , libs are supposed to be published together, unless we forgot to declare the changes using changeset for errors lib? |
The changeset for #6394 does not specify modifications to the 'errors' package, so it was not published as intended. |
Like @devfive suggest here: #6394 (comment) We should bring back |
Becoming a big issue for the community as building anything with |
Any updates on this?? Please if anyone knows |
Thanks very much. |
This still isn't on npm, after reading this thread I installed 16.4 and it didn't work after installing 16.3 finally got it work! Just as fyi until new package is out, for anyone still having this issue. |
Thanks for the updateSent from my iPhoneOn Jun 3, 2024, at 6:35 PM, PdroCorrea ***@***.***> wrote:
This still isn't on npm, after reading this thread I installed 16.4 and it didn't work after installing 16.3 finally got it work! Just as fyi until new package is out, for anyone still having this issue.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
It looks like |
|
Impacted Library name
@ledgerhq/hw-transport, @ledgerhq/errors
Impacted Library version
6.30.5, 6.16.4
Describe the bug
Error type - TransportRaceCondition used in @ledgerhq/[email protected] doesn't exist in @ledgerhq/[email protected].
Expected behavior
If I use @ledgerhq/[email protected], it works fine with @ledgerhq/[email protected].
Additional context
No response
The text was updated successfully, but these errors were encountered: