Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
reflux-rehydrate
Advanced tools
Rehydrate RefluxJS stores, to support isomorphic rendering, or loading from local storage (running offline or recovering unsaved data)
Wrapper to rehydrate RefluxJS stores
Rehydrate RefluxJS store wrapper classes, to support isomorphic rendering, or loading from local storage (running offline or recovering unsaved data)
npm install reflux-rehydrate
or yarn add reflux-rehydrate
Requires RefluxJS using the latest ES6 configuration
To do something similar with older ES5 mixins, see my fork of the Super-Simple-Flux where I've added an initWithProps tie-in on the mixin.
Use Rehydrate.createActions (Recommend for future compatibility)
import Rehydrate from 'reflux-rehydrate';
export default Rehydrate.createActions([
'myAction1', 'myAction2'
]);
Alternatively, you can just add an action called 'rehydrate' to your store.
import Reflux from 'reflux';
export default Reflux.createActions([
'rehydrate', 'myAction1', 'myAction2'
]);
Create your Store as you normally would.
In componentWillMount, initialize the store singleton using Rehydrate.initStore(MyStore)
, then call the rehydrate action with a state object containing the data to be rehydrated, for example Actions.rehydrate(this.props)
Example Code:
import Rehydrate from 'reflux-rehydrate';
import MyStore from '../stores/MyStore';
export default class MyComponent extends Reflux.Component {
componentWillMount() {
Rehydrate.initStore(MyStore); //instatiates Store singleton before Reflux normally would, and injects rehydrate action listeners
Actions.rehydrate(this.props); //all props are added to store state
}
//...
}
You can also specify just the props that should be synced to the store
Actions.rehydrate({data1: this.props.data1, data2: this.props.data1});
Be sure that the names you use in rehydrate() actually match what is expected in the store. They are simply added to the state, we are not checking to see if they match what is initialized in the constructor. However, warnings like that would be a good addition to this project at some point.
This project is using Rackt to simplify building React components https://github.com/mzabriskie/rackt-cli
FAQs
Rehydrate RefluxJS stores, to support isomorphic rendering, or loading from local storage (running offline or recovering unsaved data)
The npm package reflux-rehydrate receives a total of 18 weekly downloads. As such, reflux-rehydrate popularity was classified as not popular.
We found that reflux-rehydrate 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.