React will ___ a component into the DOM whenever its props change.
We render a component when the framework turns it into actual DOM output. Render is the foundational verb in frontend development, central to React, Vue, and others, as in "the render method." Draw and paint describe low-level browser steps, and show is too vague. Developers constantly say "this component renders" and "server-side rendering," so render a component is the precise, essential collocation for describing how UI is produced from code.
2 / 5
After server-rendered HTML loads, the framework will ___ the page to make it interactive.
To hydrate means to attach JavaScript event handlers and state to static server-rendered HTML, making it interactive. Hydrate is the precise frontend term, as in "hydration mismatch" warnings in React and Next.js. Water, wet, and soak are literal interpretations of the metaphor that no developer uses. The concept of "partial hydration" is widely discussed, so hydrate the page is the correct collocation for activating server-rendered markup on the client.
3 / 5
To improve load time, we ___ heavy components so they download only when needed.
We lazy-load resources when we defer loading them until they are actually required. Lazy-load is the standard performance term, as in "lazy loading images" or "React.lazy." Slow-load, late-load, and soft-load are not real technical terms. The native attribute loading="lazy" reinforces the vocabulary, so lazy-load components is the precise, idiomatic collocation for delaying downloads to speed up initial page rendering.
4 / 5
A build tool will ___ all the modules into a few optimised files for the browser.
To bundle means to combine many source modules into optimised output files for delivery. Bundle is the standard frontend term, behind tools named Webpack, Rollup, and esbuild, and phrases like "bundle size." Package, wrap, and box do not carry this specific build-time meaning. Developers track "the JavaScript bundle," so bundle the modules is the precise collocation for the step that prepares code for the browser.
5 / 5
Modern bundlers ___ unused code so it never ships to the user.
To tree-shake means to eliminate dead, unreferenced code from the final bundle. Tree-shaking is an established build-optimisation term, as in "tree-shakeable modules." Leaf-drop, branch-cut, and wood-chop are invented and never used. The metaphor imagines shaking a tree so dead leaves fall away, leaving only used code. So tree-shake unused code is the precise collocation for removing imports that are never actually executed.