Practise the standard verbs for splitting webpack bundles effectively.
0 / 5 completed
1 / 5
Fill in: 'We ___ vendor code into a separate chunk so browsers can cache it independently of frequently-changing app code.'
We 'split code' — the standard, established webpack collocation for dividing a bundle into separate chunks. The other options aren't the recognised term here.
2 / 5
Fill in: 'Bundling every route into a single file can ___ users downloading megabytes of code they'll never even visit.'
We say one giant bundle will 'leave' users over-downloading — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ route-level chunks with dynamic import() so each page only loads the code it actually needs.'
We 'generate chunks' — the standard, simple collocation for producing separate bundle files. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ bundle size in CI on every pull request so a new dependency doesn't silently balloon the app's weight.'
We 'measure' a size — the standard, simple collocation for evaluating a build metric. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a content hash into each chunk's filename so a cached asset only gets refetched when it actually changes.'
We 'include' a hash — the standard, simple collocation for embedding a value into a filename. The other options are less idiomatic here.