-
Notifications
You must be signed in to change notification settings - Fork 728
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
Wrong util package in dependencies #2373
Comments
Hi there, we only had this out in this constallation for 30 minutes or so, we just missed the Util release initially. Now I have also released Util v8.0.1, see #2371. So if you now install (e.g. Blockchain) the Util package should be picked up due to the |
@holgerd77 I'd expect that too. But for some reason, when I perform a fresh Wondering if this is some weird local bug on my end... |
btw, managed to fix that issue only by stating the following in my "resolutions": {
"@ethereumjs/util": "8.0.1"
} |
Hmm, we also have problems with this async event emitter fix solution we choose #2303 (comment), not yet clear how to proceed there. Eventually we just need to do another round of adopting releases anyhow. Hmm. Bit annoying. |
Yeah, I can relate to these issues you mentioned. Thanks for updating. |
@thevaizman Is this resolved with the latest release? Just want to confirm if we have more yet to do or can close this. |
So it is not yet resolved "automatically" as I still have to add this to my "resolutions": {
"@ethereumjs/util": "8.0.2"
} |
I've now also released a new Blockchain version along an EVM fix release in #2380, so this should now be mitigated, will close. |
( @thevaizman eventually it would still be re-assuring if you could give a short confirmation if easily possible ) |
hey @holgerd77, I can confirm this new release fixed the issue. thanks! :) |
The
package.json
file of theblockchain
package still has theutil
version as8.0.0
which doesn't have theLock
class in it instead of the newutil
version -8.0.1
.I can see that you merged a fix to
master
- here.Any idea when will this fix be pushed to
yarnpkg
? I can still see the wrongpackage.json
file there.cc: @holgerd77
The text was updated successfully, but these errors were encountered: