-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Remeda ESLint Plugin #656
Comments
Hello, and thanks for the kind words. I'll jump right in:
|
Thank you for clarifying the perf concerns, it totally makes sense. About ESLint, let me clarify what i wanted to express.
See? Here you would just be reimplementing the ESLint CLI functionality: |
Even Ramda has one. |
Your examples are from vanilla JS to lodash/ramda, not from one library to the other. If your project is already using Lodash, the vanilla -> Remeda is not the main hurdle to adoption, the lint rule wouldn't help in those cases. |
The point is not the Lodash > Remeda migration. That's the easy part, because most utils overlap, even by names. |
i think the eslint plugin is a good idea; is that the only feature request from this issue? if so, let's rename this issue and use it to track this? |
Yes, fine by me 👍 |
Hey, i'm following the developments of Remeda and i have to say, this looks to be the most promising Lodash alternative in the wild right now.
Many have been born trough the years but almost all of them got abandoned at some point. Apparently replacing Lodash is no easy task.
There are a few concerns that i want to raise that could be key to the widespread adoption o this lib:
The text was updated successfully, but these errors were encountered: