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
releases.json for all device models are available from two sources:
locally as json files (Suite Desktop & Suite Lite)
data.trezor.io (Suite Web, also fallback for both Desktop & Lite if local files are suspected to be outdated)
Local json files are not part of the JS bundle - they are external files, loaded by a runtime require, which may not always load successfully - I suspect that this could be the true root cause for #16725, which was resolved only superficially.
👉 Rewrite the files into TS, so that they are part of JS bundle. Those are to be maintained manually (currently, the jsons are also manually updated).
We have a CI script that checks consistency with data repo ➡ update to check the TS files.
💡 instead of yarn build:libs, this routine could be triggered as a postinstall script for better DX - so that devs won't have to run build:libs, which is time consuming
The text was updated successfully, but these errors were encountered:
releases.json
for all device models are available from two sources:json
files (Suite Desktop & Suite Lite)Local
json
files are not part of the JS bundle - they are external files, loaded by a runtimerequire
, which may not always load successfully - I suspect that this could be the true root cause for #16725, which was resolved only superficially.👉 Rewrite the files into TS, so that they are part of JS bundle. Those are to be maintained manually (currently, the jsons are also manually updated).
We have a CI script that checks consistency with data repo ➡ update to check the TS files.
💡 instead of
yarn build:libs
, this routine could be triggered as a postinstall script for better DX - so that devs won't have to run build:libs, which is time consumingThe text was updated successfully, but these errors were encountered: