remeda
ts-prune
Our great sponsors
| remeda | ts-prune | |
|---|---|---|
| 10 | 4 | |
| 3,890 | 2,019 | |
| 4.1% | - | |
| 9.3 | 0.0 | |
| 2 days ago | 5 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.
ts-prune
-
What are different ways to check for dead code/unreachable code?
I've had good experiences with ts-prune for a backend project, I'm not sure how well it will do with Angular in the mix, and it probably won't check your templates, but it might manage the rest of your code well.
-
Improving performance of large React app? And any ways to quickly identify possible opportunities for useMemo ane useCallback?
That being said. If the project is Typescript I'd recommend trying `ts-prune` which finds unused code in a project. (https://github.com/nadeesha/ts-prune) it can be really rewarding to find whole directories that are are no longer used and causing a distraction.
-
TS: Remove dead code
Happy cleaning! for more info see: https://github.com/nadeesha/ts-prune
-
How to Delete Dead Code in TypeScript Projects
Second, you will want to install ts-prune and ts-unused-exports globally, so they can be used for any project. Run these commands in a terminal:
What are some alternatives?
eslint-plugin-functional - ESLint rules to disable mutation and promote fp in JavaScript and TypeScript.
ts-unused-exports - ts-unused-exports finds unused exported symbols in your Typescript project
ramda - :ram: Practical functional Javascript
ts-toolbelt - 👷 TypeScript's largest type utility library
async-utils - Async function utils
component-elements - Create a custom element from any component with these tiny functions (2KB GZipped, ~1KB Brotli). Preact and React currently supported
tonal - A functional music theory library for Javascript
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
froebel - A strictly typed utility library.
meta-typing - 📚 Functions and algorithms implemented purely with TypeScript's type system
just - A library of dependency-free JavaScript utilities that do just one thing.
ramdaP-ts - TypeScript ramda utility functions for dealing with Promises (and a few misc others)