Skip to content
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

@trezor/connect-common@npm:0.0.32 No candidates found #12412

Closed
msteiner96 opened this issue May 15, 2024 · 2 comments
Closed

@trezor/connect-common@npm:0.0.32 No candidates found #12412

msteiner96 opened this issue May 15, 2024 · 2 comments

Comments

@msteiner96
Copy link

Hey, could you please let me know where the 0.0.32 went? I have some dependencies that don't longer work right now.

@MiroslavProchazka
Copy link
Contributor

cc @karliatto

@karliatto
Copy link
Member

@msteiner96 If you have a project that tries to use @trezor/connect-common@npm:0.0.32 watch out, you are probably using beta version of you npm dependencies.

The version 0.0.32 of @trezor/connect-common is only used by @trezor/connect-web, @trezor/connect-webextension and @trezor/connect that are tagged with beta in NPM. They should not be updated automatically by any package manager.

Anyway we are planning new beta release today or tomorrow that will fix that issue even for someone using beta tagged NPM, which is obliviously not recommended unless you want to try some latest feature, and run the risk of using a non-stable version.

And if I just try to run yarn add @trezor/connect-web it installs "@trezor/connect-common@0.0.31" which is right because 0.0.31 is tagged as latest in NPM and is the current stable release.

Could you explain a bit further how did you get to use @trezor/connect-common@npm:0.0.32 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants