
Security News
Meet Socket at Black Hat and DEF CON 2025 in Las Vegas
Meet Socket at Black Hat & DEF CON 2025 for 1:1s, insider security talks at Allegiant Stadium, and a private dinner with top minds in software supply chain security.
react-compose-wrappers
Advanced tools
This package solves the issue of many providers forcing indentation runoffs.
Here's how a simple component can evolve to:
const MyApp: React.FunctionComponent = () => {
const foo: Foo = { /* ... */ };
const bar: Bar = { /* ... */ };
const baz: Baz = { /* ... */ };
return (
<FooContext.Provider value={foo}>
<BarContext.Provider value={bar}>
<BazContext.Provider value={foo}>
<MainComponent />
</BazContext.Provider>
</BarContext.Provider>
</FooContext.Provider>
);
}
Now when the user adds a ApolloProvider
and react-intl
, we need to keep wrapping our components.
const MyApp: React.FunctionComponent = () => {
const locale = getLocale()
const messages = getMessages(locale);
const client = getApolloClient();
const foo: Foo = { /* ... */ };
const bar: Bar = { /* ... */ };
const baz: Baz = { /* ... */ };
return (
<IntlProvider locale={locale} messages={messages}>
<ApolloProvider client={client}>
<FooContext.Provider value={foo}>
<BarContext.Provider value={bar}>
<BazContext.Provider value={foo}>
<MainComponent />
</BazContext.Provider>
</BarContext.Provider>
</FooContext.Provider>
</ApolloProvider>
</IntlProvider>
);
}
This makes our component noisy and needlessly nested. This library fixes that by allowing you to specify the wrapping strategy without needing to indent or alter the rendering code:
import { composeWrappers } from 'react-compose-wrappers';
const MyApp: React.FunctionComponent = () => {
const locale = getLocale()
const messages = getMessages(locale);
const client = getApolloClient();
const foo: Foo = { /* ... */ };
const bar: Bar = { /* ... */ };
const baz: Baz = { /* ... */ };
const SuperProvider = composeWrappers([
// Note: children can be passed via children={props.children}
props => <IntlProvider locale={locale} messages={messages} children={props.children} />,
// Or the usual way of <MyComponent>{props.children}</MyComponent>
props => <ApolloProvider client={client}>{props.children}</ApolloProvider>,
props => <FooContext.Provider value={foo}>{props.children}</FooContext.Provider>,
props => <BarContext.Provider value={bar}>{props.children}</BarContext.Provider>,
props => <BazContext.Provider value={baz}>{props.children}</BazContext.Provider>,
]);
return (
<SuperProvider>
<MainComponent />
</SuperProvider>
);
}
Now when a new wrapper or provider is needed, you only need to alter that array with how the component should be wrapped.
FAQs
Compose multiple React component wrappers
We found that react-compose-wrappers demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Meet Socket at Black Hat & DEF CON 2025 for 1:1s, insider security talks at Allegiant Stadium, and a private dinner with top minds in software supply chain security.
Security News
CAI is a new open source AI framework that automates penetration testing tasks like scanning and exploitation up to 3,600× faster than humans.
Security News
Deno 2.4 brings back bundling, improves dependency updates and telemetry, and makes the runtime more practical for real-world JavaScript projects.