Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
redux-connect
Advanced tools
It allows you to request async data, store them in redux state and connect them to your react component.
How do you usually request data and store it to redux state? You create actions that do async jobs to load data, create reducer to save this data to redux state, then connect data to your component or container.
Usually it's very similar routine tasks.
Also, usually we want data to be preloaded. Especially if you're building universal app, or you just want pages to be solid, don't jump when data was loaded.
This package consist of 2 parts: one part allows you to delay containers rendering until some async actions are happening. Another stores your data to redux state and connect your loaded data to your container.
This is a fork and refactor of redux-async-connect
Using npm:
$ npm install redux-connect -S
import { Router, browserHistory } from 'react-router';
import { ReduxAsyncConnect, asyncConnect, reducer as reduxAsyncConnect } from 'redux-connect'
import React from 'react'
import { render } from 'react-dom'
import { createStore, combineReducers } from 'redux';
// 1. Connect your data, similar to react-redux @connect
@asyncConnect([{
key: 'lunch',
promise: ({ params, helpers }) => Promise.resolve({ id: 1, name: 'Borsch' })
}])
class App extends React.Component {
render() {
// 2. access data as props
const lunch = this.props.lunch
return (
<div>{lunch.name}</div>
)
}
}
// 3. Connect redux async reducer
const store = createStore(combineReducers({ reduxAsyncConnect }), window.__data);
// 4. Render `Router` with ReduxAsyncConnect middleware
render((
<Provider store={store} key="provider">
<Router render={(props) => <ReduxAsyncConnect {...props}/>} history={browserHistory}>
<Route path="/" component={App}/>
</Router>
</Provider>
), el)
import { renderToString } from 'react-dom/server'
import { match, RoutingContext } from 'react-router'
import { ReduxAsyncConnect, loadOnServer, reducer as reduxAsyncConnect } from 'redux-connect'
import createHistory from 'history/lib/createMemoryHistory';
import { Provider } from 'react-redux';
import { createStore, combineReducers } from 'redux';
app.get('*', (req, res) => {
const store = createStore(combineReducers({ reduxAsyncConnect }));
match({ routes, location: req.url }, (err, redirect, renderProps) => {
// 1. load data
loadOnServer({ ...renderProps, store }).then(() => {
// 2. use `ReduxAsyncConnect` instead of `RoutingContext` and pass it `renderProps`
const appHTML = renderToString(
<Provider store={store} key="provider">
<ReduxAsyncConnect {...renderProps} />
</Provider>
)
// 3. render the Redux initial data into the server markup
const html = createPage(appHTML, store)
res.send(html)
})
})
})
function createPage(html, store) {
return `
<!doctype html>
<html>
<body>
<div id="app">${html}</div>
<!-- its a Redux initial data -->
<script dangerouslySetInnerHTML={{__html: `window.__data=${serialize(store.getState())};`}} charSet="UTF-8"/>
</body>
</html>
`
}
applyRouterMiddleware
Thanks to @mmahalwy for a good usage example
Pass custom render
method to ReduxAsyncConnect
, it can look like this:
// on client
const component = (
<Router
render={(props) => (
<ReduxAsyncConnect
{...props}
helpers={{ client }}
filter={item => !item.deferred}
render={applyRouterMiddleware(useScroll())}
/>
)}
history={history}
routes={getRoutes(store)}
/>
);
Basically what you do is instead of using render method like:
const render = props => <RouterContext {...props} />;
you use
const render = applyRouterMiddleware(...middleware);
There are some solutions of problem described above:
Redux Connect uses awesome Redux to keep all fetched data in state. This integration gives you agility:
Also it's integrated with React Router to prevent routing transition until data is loaded.
You're welcome to PR, and we appreciate any questions or issues, please open an issue!
FAQs
It allows you to request async data, store them in redux state and connect them to your react component.
The npm package redux-connect receives a total of 5,608 weekly downloads. As such, redux-connect popularity was classified as popular.
We found that redux-connect 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.