streamich / three-ducks

Distilled Redux for gourmet developers

three-ducks

Tiny Redux clone with plugins.

• Tiny — core is only 5 lines of code, redux preset is 0.6Kb
• All Redux APIs — .subscribe(), .getState(), .dispatch(), etc. — as separate plugins
• Faster than Redux — see benchmark results
• 100% compatible — works with react-redux, passes Redux createStore() test suite
• Public domain — Unlicense license

Reference

• Installation
• Plugins
  • dispatch
  • reducer
  • subscribe
  • replaceReducer
  • getState
  • observable
  • thunk
• Presets
  • redux

See also

• nano-css — Distilled CSS-in-JS for gourmet developers

Benchmark

Running a simple "counter" micro-benchmark.

three-ducks (with redux preset) x 1,076 ops/sec ±2.58% (47 runs sampled)
redux x 494 ops/sec ±4.40% (43 runs sampled)
Fastest is three-ducks (with redux preset)

three-ducks's Issues

Dependency deprecation warning: babel-preset-es2017 (npm)

On registry https://registry.npmjs.org/, the "latest" version (v6.24.1) of dependency babel-preset-es2017 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2017's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Side-effect frameworks

• redux-thunk
• redux-saga
• redux-effects
• redux-loop
• async reducer middleware: https://ricostacruz.com/til/redux-side-effects
• funks: https://hackernoon.com/why-i-wrote-a-redux-async-outerware-277d450dba74

Summary list of many tools:

• https://github.com/markerikson/redux-ecosystem-links/blob/master/side-effects.md

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Dependency deprecation warning: babel-preset-es2015 (npm)

On registry https://registry.yarnpkg.com/, the "latest" version (v6.24.1) of dependency babel-preset-es2015 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2015's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Dependency deprecation warning: travis-deploy-once (npm)

On registry https://registry.npmjs.org, the "latest" version (v5.0.11) of dependency travis-deploy-once has the following deprecation notice:

We recommend to use Travis Build Stages instead

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about travis-deploy-once's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

typo: observalbe instead of observable

Makes store an observalbe, this allows you to use it with Rxjs, for example.

https://github.com/streamich/three-ducks/blob/master/docs/plugins/observable.md

Action required: Add a Renovate config

Hi,

You will need to add a config to this repository if you want Renovate to continue creating PRs. Renovate will soon begin skipping all repositories that don't have a valid config found, even if you've received PRs before.

To keep functionality exactly the same, you can add an empty JSON config ({}) to your repo in any of the following files: renovate.json, .github/renovate.json, .renovaterc, .renovaterc.json

Logger

logger plugin that uses redux-logger

Dependency deprecation warning: babel-preset-es2016 (npm)

On registry https://registry.npmjs.org/, the "latest" version (v6.24.1) of dependency babel-preset-es2016 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2016's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]