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
@chainsafe/blst
module not found when importing @lodestar/light-client
#6589
Comments
Note, for now, we've just added |
but i think lightclient will require bls to verify sync committee signature as most probably signed updates signatures |
Lightclient uses |
I haven't attempted this yet but seem like it should be possible with the current setup. Or perhaps we can massage the imports in |
@acolytec3 that will definitely get you going for now and is possibly the right idea long term depending on how everyone feels about the comment above. |
Good to know. Will just proceed with |
Describe the bug
I'm working through updating Ultralight to use the latest versions of various chainsafe/lodestar libraries and encountered an issue where
@chainsafe/blst
isn't found. It appears to be an indirect import of@lodestar/light-client
via@chainsafe/bls
which Ultralight also does not currently use other than as a transitive dependency.As noted here
@chainsafe/blst
is an optional/peer dep for@chainsafe/bls
but not for@lodestar/light-client
.Expected behavior
Ideally,
@lodestar/light-client
should import the correct optional dependencies for@chainsafe/bls
so downstream consumers don't need to specify this in package.jsonSteps to reproduce
No response
Additional context
Here is an example from our CI where this issue occurs.
Operating system
Linux
Lodestar version or commit hash
"@lodestar/light-client": "^1.17.0"
The text was updated successfully, but these errors were encountered: