If you want to ask something - Go to Discussions
If you found a bug - Go to Issues
📖 Big inspiration from fp-ts, @sweet-monads
- Option<T> - Forget about nulls and undefined
- Result<T, E> - Handle errors like a god
- Iter<T> - Lazy iterables with superpowers
- Schema - Pseudo pattern-matching for js
npm i kirka
# or
npm i github:numfin/kirka
# or fork it and instal from your own repo
Usage described in modules readme. All documentation inside JSDoc
(autocomplete)
Why not fp-ts?
- I tried fp-ts
- I realised they have terrible documentation.
- Using things required reading ton of types and remembering everything.
- My friend suggested trying
sweet-monads
.
Why not sweet-monads
- No documentation
- Not a lot of functionality (e.g. conversions between types)
- Typing looks weak (tons of overloads without reason)
- Lack of esm support
- Class context complexity