Skip to content
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

installation of bean-sdk requires adjusted command as latest version of one dependency no longer works #14

Open
Mr-onno opened this issue Nov 1, 2020 · 0 comments

Comments

@Mr-onno
Copy link

Mr-onno commented Nov 1, 2020

bean-sdk has a number of dependencies. These depencies are automatically installed as sub-modules by npm. For all of these dependencies but one, the version is specified in package.json. This ensures that when installing bean-sdk, compatible versions of the dependencies are also installed.

For one dependency, commander, the version is not specified and npm will install the latest version. But somewhere after July 2020, a new version of commander was released that is no longer compatible with bean-sdk.

Therefore, you need to tell npm to use a specific version of commander when installing bean-sdk.
This can be done in the following way:

npm install -g --unsafe-perm [email protected] bean-sdk

The makers of bean-sdk can correct this in the npm package, but as the lightblue bean is no longer supported, I assume this will not happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant