docs/third-parties: explain connect dependencies

pull/975/head
Tomas Susanka 4 years ago
parent 20d66adddd
commit 2ccb3aa04e

@ -24,10 +24,28 @@ _Updating HWI to the latest version should be enough._
- Blockstream Green iOS https://github.com/Blockstream/green_ios
### Using Connect:
_This usually only requires updating Connect to the latest version._
See https://github.com/trezor/connect/network/dependents for a full list
of projects depending on Connect.
_See https://github.com/trezor/connect/network/dependents for a full list
of projects depending on Connect._
#### Connect dependencies introduction
Javascript projects that have Connect as a dependency are using the [Connect NPM
package](https://www.npmjs.com/package/trezor-connect) on version specified in their
yarn.lock (or similar). This NPM package is not a complete Connect library, it is a
simple layer that deals with opening an iframe and loading the newest Connect from
connect.trezor.io.
Such project must have the newest MAJOR version of this NPM package (v8 at the moment).
But then the main logic library (dealing with devices etc.) is fetched from
connect.trezor.io and is therefore under our control and can be updated easily.
So in a nutshell:
- If there is a new MAJOR version of Connect we indeed want to notify these parties below.
- In other cases we do not, we just need to deploy updated Connect before releasing
firmwares.
#### Notable third-parties
- Exodus (closed source)
- MagnumWallet (closed source)

Loading…
Cancel
Save