Open gagdiez opened 1 month ago
Just to add onto this, the issue is seen only while using yarn, I have not seen it when using npm or pnpm. Maybe that's a good place to start looking into it.
A potential fix https://t.me/neardev/53025 , the idea is to remove NAJ yarn remove near-api-js
and then install it again yarn add near-api-js@4.0.3
in wallet-selector project.
Somehow yarn.lock
there contains some wrong versions of dependencies this should fix them.
Node v22.5.1
Yarn v1.22.19
Hey guys,
the issue is related to here-wallet
because @here-wallet/core@1.6.6
use near-api-js@3.0.4
.
I will try to find a solution asap.
Thanks for provided info ... helped me a lot.
few more:
mintbase-wallet
use near-api-js@3.0.4
near-mobile-wallet
use @peersyst/near-mobile-signer@1.0.12
who use near-api-js@2.1.4
If you are using @near-wallet-selector/here-wallet, the workaround could be to specifically set these resolutions or overrides to ensure compatibility with near-api-js@^4.0.0.
This approach forces the usage of the newer version of near-api-js throughout your project.
However, please note that this is a temporary workaround and not an ideal long-term solution.
For npm, you can use overrides in your package.json like this:
"overrides": {
"near-api-js": "^4.0.0"
}
For Yarn, you can use resolutions in your package.json like this:
"resolutions": {
"near-api-js": "^4.0.0"
}
Hope this help.
Prerequisites
near-api-js
.Description
Multiple people is reporting that some of our examples have stopped working when using the latest version of
near-api-js
andwallet-selector
.Reproducible demo
https://github.com/near-examples/guest-book-examples/tree/main/frontend
Steps to reproduce
yarn install
on the frontendyarn dev
Expected behavior
A transaction saving the message should be triggered, and thus the message saved
Actual behavior
Your environment
Self-service