Closed hidde-jan closed 4 years ago
It seems that none of the issues on Github actually get a reply from the developers. The repository for the jolocom-registry-contract package is actually deprecated and replaced by a mono repo, so it seems the dependency is quite an older version. Are there any plans to support newer versions of node with the jolocom-lib package?
Thanks for the attempt but None of the developers have responded..Sad! It would be nice if there was a replacement project with more stable development.
It seems that none of the issues on Github actually get a reply from the developers. The repository for the jolocom-registry-contract package is actually deprecated and replaced by a mono repo, so it seems the dependency is quite an older version. Are there any plans to support newer versions of node with the jolocom-lib package?
jolocom-lib
will support newer versions of node in an upcoming release.
There are (currently) no plans to backport support for later versions of node on the current (4.x) jolocom-lib
Describe the bug
The jolocom-lib depends on a deprecated version of jolocom-registry-contract, which pulls in all kinds of ancient dependency versions. This leads to install problems for node versions later than 10 (scrypt for instance through some web3 and ethereum wallet dependencies).
To Reproduce Steps to reproduce the behavior:
Expected behavior
Being able to cleanly install on newer versions of nodejs
Desktop (please complete the following information):