THthunderbong·Aug 22, 2019
I guess the reason this is getting downvoted is because there isn't sufficient information in the comment. It's true, however.
I find this is rampant in the Node community - For any small feature, rather than making a PR or suggesting changes to the original module (maybe via an option), the goal is to create a new library.
I feel what the Node community doesn't realize is that this creates a dependency hell where I can't run my programs which were running a week back, by pulling in the latest libraries.
Another example I came across recently was redux-thunk[0], which is used practically wherever redux is used. All it does is add a callback!
This is entire code of redux-thunk library!
function createThunkMiddleware(extraArgument) {
return ({ dispatch, getState }) => next => action => {
if (typeof action === 'function') {
Read the rest
return action(dispatch, getState, extraArgument);
}
return next(action);
};
}
const thunk = createThunkMiddleware();
thunk.withExtraArgument = createThunkMiddleware;
export default thunk;
[0]: https://github.com/reduxjs/redux-thunk