
Research
NPM targeted by malware campaign mimicking familiar library names
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
redux-offline-queue-too
Advanced tools
Simple offline queue for redux, inspired by redux-offline-queue.
Forked from redux-offline-queue
made by InspireNL.
This package is a simple solution for handling actions or requests with redux while the app is in an offline state by queueing these, and dispatching them once connectivity is re-established. Works perfect with react-native
Motivation: Provide a better user experience.
npm install --save redux-offline-queue-too
redux-offline-queue
See example project here: offlineTweet
Get up and running in 4 easy steps:
Either import the { reducer as offlineQueue }
from redux-offline-queue
and add it to the combineReducers
or require it like so (whatever floats your boat):
import { combineReducers } from 'redux';
export default combineReducers({
offlineQueue: require('redux-offline-queue').reducer,
yourOtherReducer: require('~App/yourOtherReducer').reducer,
});
import { offlineMiddleware } from 'redux-offline-queue';
const composeStoreWithMiddleware = applyMiddleware(offlineMiddleware())(
createStore
);
Note that this queue is not persisted by itself. One should provide a persistence config by using e.g. redux-persist
to keep the offline queue persisted.
reduxsauce
import { createReducer, createActions } from 'reduxsauce'
import { markActionsOffline } from 'redux-offline-queue'
const { Types, Creators } = createActions({
requestBlogs: null,
createBlog: ['blog'],
})
markActionsOffline(Creators, ['createBlog'])
...
import { markActionsOffline } from 'redux-offline-queue'
const Creators = {
createBlog: blog => ({
type: 'CREATE_BLOG',
blog,
}),
}
markActionsOffline(Creators, ['createBlog'])
...
Last but not least...
import { OFFLINE, ONLINE } from 'redux-offline-queue';
if (appIsConnected) {
dispatch({ type: ONLINE });
} else {
dispatch({ type: OFFLINE });
}
Works perfect with React Native's NetInfo
import { put, take, call } from 'redux-saga/effects';
import { NetInfo } from 'react-native';
import { OFFLINE, ONLINE } from 'redux-offline-queue';
function* startWatchingNetworkConnectivity() {
const channel = eventChannel(emitter => {
NetInfo.isConnected.addEventListener('connectionChange', emitter);
return () =>
NetInfo.isConnected.removeEventListener('connectionChange', emitter);
});
try {
for (;;) {
const isConnected = yield take(channel);
if (isConnected) {
yield put({ type: ONLINE });
} else {
yield put({ type: OFFLINE });
}
}
} finally {
channel.close();
}
}
Android
If react native's NetInfo
is intended to be used, for android don't forget to add the following to the AndroidManifest.xml
:
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
Inspired by redux-queue-offline(mathieudutour)
Developed by Krzysztof Ciombor
redux-saga
If you are using redux-sagas
for http requests and want to fire your redux actions normally, but suspend(queue) sagas, for Step 2, do the following instead:
import { applyMiddleware } from 'redux';
import createSagaMiddleware from 'redux-saga';
import {
offlineMiddleware,
suspendSaga,
consumeActionMiddleware,
} from 'redux-offline-queue';
const middleware = [];
middleware.push(offlineMiddleware());
const suspendSagaMiddleware = suspendSaga(createSagaMiddleware());
middleware.push(suspendSagaMiddleware);
middleware.push(consumeActionMiddleware());
applyMiddleware(...middleware);
It is IMPORTANT that the consumeActionMiddleware
is placed last, so you can allow the previous middlewares to react first before eventually getting consumed.
Additional configuration can be passed with offlineMiddleware()
, such as adding additional triggers that will trigger the offline queue to dispatch its actions:
...
import { REHYDRATE } from 'redux-persist'
applyMiddleware(offlineMiddleware({
additionalTriggers: REHYDRATE,
}))
...
FAQs
Simple offline queue for redux, inspired by redux-offline-queue.
The npm package redux-offline-queue-too receives a total of 7 weekly downloads. As such, redux-offline-queue-too popularity was classified as not popular.
We found that redux-offline-queue-too 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.
Research
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
Research
Socket's research uncovers three dangerous Go modules that contain obfuscated disk-wiping malware, threatening complete data loss.
Research
Socket uncovers malicious packages on PyPI using Gmail's SMTP protocol for command and control (C2) to exfiltrate data and execute commands.