@evanion/compose
v1.0.8
Published
React component that allows you to get out of Provider hell
Downloads
12
Maintainers
Readme
compose
A React component that allows you to cleanup your providers.
Raise your hand if your App.tsx
looks like this
const App: React.FC = () => {
return (
<ErrorBoundary>
<CacheProvider value={emotionCache}>
<ThemeProvider theme={theme}>
<TranslationProvider locale={locale} messages={messages}>
<StateProvider state={stateStore}>
<CoffeeProvider>
<SanityProvider>
<Routes />
</SanityProvider>
</CoffeeProvider>
</StateProvider>
</TranslationProvider>
</ThemeProvider>
</CacheProvider>
</ErrorBoundary>
);
};
This package let's you go to this:
import { Provider, ComposeProvider } from "@evanion/compose";
const providers: Provider[] = [
ErrorBoundary,
[CacheProvider, { value: emotionCache }],
[ThemeProvider, { theme }],
[TranslationProvider, { locale, messages }],
[StateProvider, { state: stateStore }],
CoffeeProvider,
SanityProvider,
];
const App: React.FC = () => {
return (
<ComposeProvider providers={providers}>
<Routes />
</ComposeProvider>
);
};
In previous versions of the documentation, the documentation said that the prop should be called providers
but the code expected components
. This has been fixed in version 1.0.4. And ComposeProvider
now accepts either providers
or components
as a prop. Sorry for the inconvenience.