We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Setting up a development environment should work flawlessly, without errors.
Developers are confronted with a missing instruction:
The required Node.js version to use:
Using the latest stable Node.js will yield:
Unsupported engine { required: { node: '>=12.13.0 <=12', npm: '>=6.12.0' } }
Developers are confronted with dependency problems:
One of the peer dependencies causes an error unless installed (related to chart.js)
related to chart.js
The npm install command hangs indefinitely (related to trezor-connect / trezor.js)
related to trezor-connect / trezor.js
$ git clone https://github.com/LiskHQ/lisk-desktop.git $ cd lisk-desktop $ npm install <-- Hangs here, obviously...
MacOS Big Sur v11.5.2
Intel
v2.0.1
The text was updated successfully, but these errors were encountered:
Merge pull request #3790 from LiskHQ/3789-unable-to-setup-development…
4090389
…-environment Unable to setup development environment - Closes #3789
ikem-legend
Successfully merging a pull request may close this issue.
Expected behavior
Setting up a development environment should work flawlessly, without errors.
Actual behavior
Developers are confronted with a missing instruction:
The required Node.js version to use:
Using the latest stable Node.js will yield:
Developers are confronted with dependency problems:
One of the peer dependencies causes an error unless installed (
related to chart.js
)The npm install command hangs indefinitely (
related to trezor-connect / trezor.js
)Steps to reproduce
Which version(s) does this affect? (Environment, OS, etc...)
MacOS Big Sur v11.5.2
Intel
v2.0.1
The text was updated successfully, but these errors were encountered: