Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
react-context-api-store
Advanced tools
An HOC state management inpired by redux implemented using react's context api.
This library is actively being maintained by the developer. Feature requests, enhancements, and bug reports are all welcome to the issue section.
Seemless, light weight, state management library that comes with asynchronous support out of the box. Inspired by Redux and Vuex. Built on top of React's context api.
5kb transpiled, not minified.
When you want a state management that's small and supports asynchronous actions out of the box.
https://aprilmintacpineda.github.io/react-context-api-store/#/
npm install react-context-api-store
yarn add react-context-api-store
Usage is the same as with redux. Except I used React's new Context API in version 16.3.0. I also simplified some stuff. If you've used Redux and Vuex in the pass, everything here will be familiar to you.
Make sure to read and understand all the notes here after as they convey a very important message.
Provider
First, import react-context-api-store
as Provider
. The Provider is a component that accepts a prop called store
. You would use this component as your top most component.
import React from 'react';
import { render } from 'react-dom';
import { BrowserRouter, Route, Link, Switch } from 'react-router-dom';
import Provider from 'react-context-api-store';
class App extends React.Component {
render () {
return (
<Provider store={store}>
<BrowserRouter>
<div>
<ul>
<li>
<Link to="/todos">Todos</Link>
</li>
<li>
<Link to="/">Home</Link>
</li>
</ul>
<Switch>
{
routes.map((route, i) => <Route key={i} {...route} />)
}
</Switch>
</div>
</BrowserRouter>
</Provider>
);
}
}
render(
<App />,
document.querySelector('#app')
);
store
The store is simply a JS object where your global states would live.
{
userState: {
username: defaultUsername
},
todos: [...defaultTodos],
anotherState: valueHere,
oneMoreState: oneMoreValue
};
Then you pass this as the store
prop to the provider.
The provider always assume that the store is an object and no checks were added to minimize the file size. Making sure that you pass an object as the store
is up to you.
Works the same way as with redux, with a little bit of change. You import { connect }
from the react-context-api-store
package. Connect is an HOC that wraps your component with the Provider.Consumer
and passes all the states and actions to the component as properties.
Connect
accepts two parameters. The first parameter is a callback function
that will receive the store's current state
. It should return an object that maps all the states that you want the component to have.
example code
function mapStateToProps (state => {
console.log(state);
return {
// .. all the state that I want
user: state.user,
todos: state.todos
}
})
The second parameter is an object containing all the functions that will serve as the action. This is typically what you call when the user clicks a button or a particular event occured. The action will receive the original parameters given to it, except it will receive an object as the first parameter, this object is provided by the dispatcher
. The object contains two things, (1) the store's state and (2) a function called updateStore
. The updateStore
function is what you call when you want to update the state, you need to give it an object of the states that you want to update, the rest that you did not touch will remain unchanged and intact.
example code
// somewhere in your component
<input
type="checkbox"
checked={todo.isDone}
onChange={e => this.props.updateTodoDone(e.target.checked, todo.value, i)}
/>
// the second parameter
const actions = {
updateTodoDone (store, isDone, targetValue, targetIndex) {
store.updateStore({
todos: store.state.todos.map((todo, todoIndex) => {
if (todo.value != targetValue || todoIndex != targetIndex) return todo;
return {
...todo,
isDone
};
})
});
}
}
Over all, you'll have something like this:
import React from 'react';
import PropTypes from 'prop-types';
import { connect } from 'react-context-api-store';
/**
* in this example, all the action handlers are in the
* ../store/index.js but it does matter where you store them,
* they are just functions that when executed gains access to the
* store.
*/
import { updateTodoDone, deleteTodo, addTodo } from '../store';
class Todos extends React.Component {
state = {
newTodoValue: ''
}
handleNewTodoSubmit = (e) => {
e.preventDefault();
return this.props.addTodo(this.state.newTodoValue, () => this.setState({
newTodoValue: ''
}));
}
addTodoForm = () => {
return (
<form onSubmit={this.handleNewTodoSubmit}>
<input
type="text"
value={this.state.newTodoValue}
onChange={e => this.setState({
newTodoValue: e.target.value
})}
/>
<input type="submit" value="Add todo" />
</form>
);
}
render () {
if (!this.props.todos.length) {
return (
<div>
{this.addTodoForm()}
<h1>Hi {this.props.userState.username}, your todo list is empty.</h1>
</div>
);
}
return (
<div>
{this.addTodoForm()}
<h1>Hi {this.props.userState.username}, {'here\'s your todo list'}.</h1>
{
this.props.todos.map((todo, i) =>
<div key={i} style={{ marginBottom: '10px' }}>
<span
style={{ cursor: 'pointer', userSelect: 'none', backgroundColor: 'red', color: 'white', marginRight: '2px', borderRadius: '2px', padding: '1px' }}
onClick={() => this.props.deleteTodo(todo.value, i)}>x</span>
<label style={{ cursor: 'pointer', userSelect: 'none' }}>
<input
type="checkbox"
checked={todo.isDone}
onChange={e => this.props.updateTodoDone(e.target.checked, todo.value, i)}
/>
{
todo.isDone?
<span style={{ color: 'red', textDecoration: 'line-through' }}>
<span style={{ color: 'gray' }}>{todo.value}</span>
</span>
: <span>{todo.value}</span>
}
</label>
</div>
)
}
</div>
);
}
}
export default connect(store => ({
userState: store.userState,
todos: store.todos
}), {
updateTodoDone,
deleteTodo,
addTodo,
// you could also add something else here
anotherAction (store) {
/**
* if your action handler does not call store.updateState();
* nothing will happen to the state
*/
console.log(store);
}
})(Todos);
The package itself does not care how you handle this, you can use async/await
if you like or stick to the chained .then
of promises. But don't use generator functions as the store package was not equipped with it and supporting it is not an option because it would defeat the whole purpose of this library.
example code
function myStateHandler (store, data) {
store.updateState({
aState: {
...store.state.aState,
loading: true
}
});
fetch('/somewhere')
.then(response => response.json())
.then(response => {
// do something with the response
store.updateState({
aState: {
...store.state.aState,
loading: false,
data: { ...response.data }
}
});
});
}
FAQs
Seemless, lightweight, state management library that supports async actions and persistent states out of the box. Inspired by Redux and Vuex. Built on top of React's context api.
The npm package react-context-api-store receives a total of 2 weekly downloads. As such, react-context-api-store popularity was classified as not popular.
We found that react-context-api-store 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
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.