eslint-plugin-functional VS remeda

It recommend using https://github.com/eslint-functional/eslint-plugin-functional to force readonly on all properties.

Here's one the PRs that this issue happens with: https://github.com/eslint-functional/eslint-plugin-functional/pull/397

Here's the CI log link.

Also add this no-mutation ESLint rule as extra protection https://github.com/jonaskello/eslint-plugin-functional/blob/master/docs/rules/immutable-data.md

I just use https://github.com/jonaskello/eslint-plugin-functional

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.

Remeda's pipe implementation

I saw this trending a few days ago: https://github.com/remeda/remeda

Also heard that Remeda is better for TS.

Remeda - a utility library that provides a set of functions that will help us deal with strings, objects and arrays

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.