Performance Code Splitting

Code splitting for Trezor Suite web and desktop — what belongs behind `import()` or `React.lazy`, where the boundary goes, how a failed chunk load and its retry behave, and the production-build measurement that proves a split. Use when adding a dependency or a feature that not every user opens, when writing `import()` or `React.lazy`, or when checking how a change affects bundle size.

trezor Updated

File contents

trezor/trezor-suite commit 6cda1c4ff6

Frequently asked questions

npx get-skill add trezor/performance-code-splitting