Gathering detailed insights and metrics for redux-thunk-subscribe
Gathering detailed insights and metrics for redux-thunk-subscribe
Gathering detailed insights and metrics for redux-thunk-subscribe
Gathering detailed insights and metrics for redux-thunk-subscribe
npm install redux-thunk-subscribe
Typescript
Module System
Node Version
NPM Version
63.3
Supply Chain
71.5
Quality
75.3
Maintenance
100
Vulnerability
100
License
JavaScript (100%)
Total Downloads
80,606
Last Day
1
Last Week
12
Last Month
41
Last Year
2,269
7 Stars
6 Commits
3 Forks
4 Watching
1 Branches
5 Contributors
Minified
Minified + Gzipped
Latest Version
1.0.3
Package Id
redux-thunk-subscribe@1.0.3
Size
2.89 kB
NPM Version
3.10.10
Node Version
7.2.1
Publised On
17 Apr 2017
Cumulative downloads
Total Downloads
Last day
0%
1
Compared to previous day
Last week
100%
12
Compared to previous week
Last month
-46.1%
41
Compared to previous month
Last year
68.2%
2,269
Compared to previous year
Similar to Redux Thunk, but with subscribe
available to thunks (in addition to dispatch
and getState
) so they can add listeners to the store on-the-fly.
Important note: if you just need asynchonous actions, you probably should be using Redux Thunk instead!
npm install --save redux-thunk-subscribe
1var createStore = require("redux").createStore; 2var thunkSubscribeEnhancer = require("redux-thunk-subscribe"); 3 4var store = createStore(reducer, thunkSubscribeEnhancer); 5 6var thunkExclamationPoint = function () { 7 return function (dispatch, getState, subscribe) { 8 console.log("thunk!"); 9 }; 10}; 11 12store.dispatch(thunkExclamationPoint());
Why make store.subscribe
available to action creators (thunks)?
Redux is normally used to build UIs, which are "complete" applications in the sense that no code is expected to be supplied by the application's users. In a UI, the consumer of store.subscribe
can simply be hard-coded (usually to React). Library code is different. Often, libraries expect users to supply certain pieces of code; a common example is an event handler where the user specifies a callback function. I like the Redux philosophy a lot, and in my opinion it is a good fit for library code. However, in library code, consumers of store.subscribe
are not always known in advance, and, in some cases, they are intended to be defined by the library's users. This creates a problem: where does the library save the callbacks?
One option is to put the user-created callbacks in the Redux store, along with the other data. However, since the callbacks are not serializable, this breaks some nice features of Redux. Putting callbacks in the store also just feels wrong: the callbacks themselves are not really state per se, but rather observers of the state.
I think a better solution is to make store.subscribe
available to action creators, so that they can set up store listeners (i.e., user-supplied callbacks) on-the-fly. That's what this library does. Since subscribe
is not included in Redux's middleware API, this library is a store enhancer that changes the thunk signature from (dispatch, getState)
to (dispatch, getState, subscribe)
.
npm test
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 0/6 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2024-12-16
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More