Repository
Current version released
3 months ago
Versions
- v2.3.0Latest
- v2.2.0
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.0
- v1.20.0
- v1.19.2
- v1.19.1
- v1.19.0
- v1.18.0
- v1.17.0
- v1.16.0
- v1.15.0
- v1.14.2
- v1.14.1
- v1.14.0
- v1.13.0
- v1.12.4
- v1.12.3
- v1.12.2
- v1.12.1
- v1.12.0
- v1.11.1
- v1.11.0
- v1.10.2
- v1.10.1
- v1.10.0
- v1.9.0
- v1.8.5
- v1.8.4
- v1.8.3
- v1.8.2
- v1.8.1
- v1.8.0
- v1.7.0
- v1.7.0-next.0
- v1.6.0-next.0
- v1.5.0-next.0
- v1.4.0-next.1
- v1.4.1
- v1.4.0-next.0
- v1.3.0-next.1
- v1.3.0-next.0
- v1.2.0-next.2
- v1.2.0-next
☄️ Effector operators library delivering modularity and convenience
- 🎲 Try it online: StackBlitz | Codesandbox | Playground
- 📚 Read documentation: patronum.effector.dev
- 📦 Source: JSdeliver | Unpkg | NPM | GitHub
- 🦉 Say about it: Twitter
💿 Install now
Please, review documentation for YOUR version of patronum not the latest. Find and open tag/release for your version and click on the tag vA.B.C to view repo and documentation for that version, or use “Switch branches/tags” selector.
npm install patronum
# or
yarn add patronum
# or
pnpm add patronum
Next just import methods from "patronum"
and use it:
import { createEffect } from 'effector';
import { status } from 'patronum';
const userLoadFx = createEffect();
const $status = status({ effect: userLoadFx });
You can read more at documentation.
Migration guide
Patronum had 3 breaking changes: 1) from 0.14
to 0.100
, 2) from 0.100
to 0.110
, 3) from 0.110
to 1.0
We have migration guide.
Development
You can review CONTRIBUTING.md
Release process
- Check out the draft release.
- All PRs should have correct labels and useful titles. You can review available labels here.
- Update labels for PRs and titles, next manually run the release drafter action to regenerate the draft release.
- Review the new version and press “Publish”
- If required check “Create discussion for this release”