remeda
refute
Our great sponsors
remeda | refute | |
---|---|---|
10 | 3 | |
3,912 | 9 | |
4.7% | - | |
9.3 | 5.9 | |
6 days ago | 6 months ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
remeda
-
Ramda: A practical functional library for JavaScript programmers
Personally I just don't think Ramda fits really well with JavaScript's mutable and often object-oriented nature. It goes against the grain too much for my taste, and it doesn't work very well with Typescript.
In a professional setting I will probably always reach for Lodash due to it's maturity and mindshare. Personally, though, I really prefer Remeda (https://github.com/remeda/remeda) as a pragmatic and flexible API.
- Functional Programming in JavaScript with Ramda.js
-
Implementing the Pipe Operator in TypeScript
Remeda's pipe implementation
-
A Typescript-first alternative to Lodash/Underscore
I saw this trending a few days ago: https://github.com/remeda/remeda
-
Ramda and Typescript Issues
Also heard that Remeda is better for TS.
- The first data utility library designed especially for TypeScript
-
How to create a Widget Grid using React
Remeda - a utility library that provides a set of functions that will help us deal with strings, objects and arrays
- A generically typed pipe function in TypeScript
-
Avoiding legacy systems
The good news is: Not all is lost. The messages are still there if you take a look at the commits of the PR. It's just a little harder to backtrack. Here is one example of a commit I made that has tons of information (even with a link!) that got squashed away.
refute
-
Ramda: A practical functional library for JavaScript programmers
I find straight forward, dedicated combinators much more readable and practical to use ie. for iterables (context where it makes a lot of sense) [0] example [1], runtime assertions (through refutations, which are much faster than combinators over assertions) [2], parser combinators for smallish grammars [3] etc.
In many cases vanilla/imperative js is more readable and terse, no need to bring functional fanaticism everywhere, just in places where it gives true benefits and in form that can be understood by peers.
Functional code can be beautiful and can also be unreadable/undebugable. Same with imperative code. It's great in js/ts you can pick approach where the problem is expressed more naturally and mix it at will.
[0] https://github.com/preludejs/generator
[1] https://observablehq.com/@mirek/project-euler
[2] https://github.com/preludejs/refute
[3] https://github.com/preludejs/parser
-
Ask HN: Why isn't JSON-RPC more widely adopted?
We use jsonrpc over websockets in production for many years in trading services. It works very well. We use lightweight libraries that look like this [0] and this [1]. It's lightweight, fast, type safe, easy to maintain and debug etc.
[0] https://github.com/preludejs/jsonrpc
[1] https://github.com/preludejs/refute
-
An Inconsistent Truth: Next.js and Typesafety
Types can be asserted at runtime (parsed) at IO boundaries (reading http request or response, websocket message, parsing json file etc). Once they enter statically type system they don't need to be asserted again.
The difference it makes is illusion of type-safety vs type-safety this article touches on.
You can try to bind service with client somehow but in many cases this will fail in production as you can't guarantee paired versioning, due to normal situations by design of your architecture or temporary mid-deployment state or other team doing something they were not suppose to do etc. It's hard to avoid runtime parsing in general.
Functional combinators [0] or faster [1] with predicate/assert semantics work very well with typescript, which is very pleasant language to work with.
[0] https://github.com/appliedblockchain/assert-combinators
[1] https://github.com/preludejs/refute
What are some alternatives?
eslint-plugin-functional - ESLint rules to disable mutation and promote fp in JavaScript and TypeScript.
assert-combinators - Functional assertion combinators.
ts-prune - Find unused exports in a typescript project. 🛀
next-rpc - makes exported functions from API routes accessible in the browser. Just import your API function and call it anywhere you want.
ramda - :ram: Practical functional Javascript
parser - String parser combinators
async-utils - Async function utils
sick - Streams of Independent Constant Keys
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
gradual-typing-bib - A bibliography on Gradual Typing
tonal - A functional music theory library for Javascript
froebel - A strictly typed utility library.