You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered: