Package Exports

@trezor/connect-common
@trezor/connect-common/files/bridge/releases.json
@trezor/connect-common/files/coins-eth.json
@trezor/connect-common/files/coins.json
@trezor/connect-common/files/firmware/t1b1/releases.json
@trezor/connect-common/files/firmware/t2b1/releases.json
@trezor/connect-common/files/firmware/t2t1/releases.json
@trezor/connect-common/files/firmware/t3b1/releases.json
@trezor/connect-common/files/firmware/t3t1/releases.json
@trezor/connect-common/files/firmware/t3w1/releases.json
@trezor/connect-common/lib/index.js
@trezor/connect-common/lib/storage
@trezor/connect-common/lib/storage.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@trezor/connect-common) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@trezor/connect-common

Collection of assets and utilities used by @trezor/connect* packages.

files

bridge

Data in releases.json are used to determine which version of Bridge to use depending on the user's operating system.

firmware

Binaries of the latest versions of firmware for each Trezor model are included in this package so that they are available to users of Suite desktop app without connecting to the internet. The process of adding new firmwares is described here. Besides the latest versions, T1B1 and T2T1 both require a transitory version for upgrading from old firmware (intermediary firmware trezor-inter-1.10.0.bin for T1B1 and version trezor-2.1.1.bin for T2T1).

There is a releases.json file for each Trezor model which must be updated any time new binaries are added. This file provides data about all available firmware versions and it is used to display them in Suite and to make sure that the correct firmware is downloaded. Read more about releases.json and it's structure here

JSPM