Context
/ˈkɒnˌtɛkst/
n. “Sharing state without prop-drilling chaos.”
Context in React is an API that allows data to be passed through the component tree without manually passing props at every level. It is designed to solve the problem of “prop-drilling,” where intermediate components receive props only to pass them down to deeper components that actually need the data.
React-Redux
/riˈækt riˈdʌks/
n. “Bridging React and Redux with sanity intact.”
React-Redux is the official binding library that connects React components to a Redux store. It provides a set of utilities and hooks that allow React components to read from the Redux state and dispatch actions without manually subscribing to the store, keeping the UI and state in sync with minimal boilerplate.
React-Query
/riˈækt ˈkwɛri/
n. “Data fetching without the drama.”
React Query is a data-fetching and state synchronization library for React applications. It simplifies the management of server state — that is, data that lives on a backend API or database — and keeps it in sync with the UI without the need for complex Redux setups or manual caching.
Redux
/ˈriːˌdʌks/
n. “Predictable state. Fewer surprises.”
Redux is a state management library for JavaScript applications, most commonly used with React. Its core purpose is to centralize application state, making it predictable, traceable, and easier to debug. In complex applications, juggling state across multiple components can quickly become chaotic — Redux offers a structured solution.
React-Router
/riˈækt ˈruːtər/
n. “Maps your components to the URL without breaking a sweat.”
React Router is a declarative routing library for React, allowing developers to build single-page applications (SPAs) with multiple views that respond to changes in the URL. Unlike traditional page reloads, React Router enables seamless navigation while keeping the application state intact.