Context Without a Provider
What you'll learn: What happens when you try to consume a Context that has no Provider above it in the component tree.
The Missing Provider Scenario
You've created a Context with createContext and are calling useContext in a component, but there's no <Provider> wrapping that component in the tree above it. What happens?
React uses the default value you passed to createContext.
This is actually one of the main reasons that first argument to createContext exists — as a fallback when no Provider is found.
How It Works
const ThemeContext = createContext('light'); // default: 'light'
function Button() {
const theme = useContext(ThemeContext);
// theme is 'light' because no Provider exists
return <button className={theme}>Click me</button>;
}
// No Provider wrapping Button!
<Button />
Without a Provider, theme becomes 'light' — the default from createContext.
Why This Matters
This behavior is useful for:
- Testing components in isolation without wrapping every test in a Provider
- Progressive migration where you add Providers gradually
- Library defaults where the Context works standalone but can be customized
But it can also hide bugs — if you forget the Provider, your component silently uses defaults instead of crashing, which might not be what you want.
The undefined Trick
Many developers intentionally pass undefined as the default:
const UserContext = createContext(undefined);
Now if you forget the Provider, user will be undefined, making the mistake obvious when you try to access user.name.
Key Takeaway: Without a Provider, useContext returns the default value from createContext. Passing undefined as the default helps catch missing Providers early.