remeda
parser
| remeda | parser | |
|---|---|---|
| 10 | 4 | |
| 3,922 | 5 | |
| 3.0% | - | |
| 9.3 | 7.7 | |
| 4 days ago | 22 days 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.
parser
-
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
-
Parsing Text with Nom
Parser combinators are great, we're using parser combinators in production, they are great ie. for typescript [0].
[0] https://github.com/preludejs/parser
- Parser Combinators in Haskell
- Casual Parsing in JavaScript
What are some alternatives?
eslint-plugin-functional - ESLint rules to disable mutation and promote fp in JavaScript and TypeScript.
instaparse
ts-prune - Find unused exports in a typescript project. 🛀
pyparsing - Python library for creating PEG parsers
ramda - :ram: Practical functional Javascript
assert-combinators - Functional assertion combinators.
async-utils - Async function utils
three-pass-compiler - Solution to the Three Pass Compiler kata on CodeWars, parsing and manipulating a very simple AST
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
parser-combinators - Parser combinators.
tonal - A functional music theory library for Javascript
angstrom - Parser combinators built for speed and memory efficiency