<Fragment>, alternatively written as <>...</>, lets you group multiple JSX nodes together.
<Profiler> lets you measure the rendering performance of a React tree programmatically.
<Suspense> lets you display a fallback while the child components are loading.
<StrictMode> enables extra development-only checks that help you find bugs early.
<DeferredValue> While primarily used as a hook (useDeferredValue), the concept is built into the React engine to help you defer updating a non-urgent part of the UI. This is often used to keep an input field responsive while a heavy list filters in the background.
Metadata Components React 19 introduced built-in support for rendering document metadata tags anywhere in your component tree. React will automatically hoist these to the <head> of the HTML document.
How would you use React.Fragment to return multiple sibling elements without adding extra DOM nodes?
If you wrap a lazily loaded component with <Suspense>, what does the fallback prop do, and when does it appear?
What happens if you pass a non‑standard HTML attribute to a built‑in element like <div>?
You added a <Suspense> wrapper around a lazy component but the fallback never shows during a slow network request. What could be causing this and how would you fix it?
When you enable <StrictMode> in development, certain lifecycle methods run twice. Explain why this happens and how you would adjust your code if needed.
You need to measure render performance of a component. Which built‑in component would you use and what steps would you take to interpret its data?
Your application uses many portals for modals and tooltips, and you start seeing memory leaks after navigating between routes. How would you investigate and resolve portal‑related leaks?
The team wants to adopt React.StrictMode globally across a large codebase. What trade‑offs should you consider, and how would you ensure existing components continue to work correctly?
You are collecting performance metrics with <Profiler> across multiple pages. How would you design a system to aggregate this data without impacting user experience?
Across several repositories, the organization wants to standardize the use of React.Fragment versus the <> shorthand. What guidelines would you establish and how would you enforce them at scale?
Looking ahead to future React releases, how would you plan for potential deprecation or changes to built‑in components like SuspenseList in a legacy codebase?
When migrating a large legacy application from class components to functional components, how would you decide which built‑in components to replace with newer APIs (e.g., using Suspense for data fetching) while minimizing risk?