You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the difference between this project and the grunt-contrib-eslint?
The readme contains absolutely no information about the difference, but the npm install results for grunt-contrib-eslint say it's been deprecated and I should now install this.
If you're going to deprecate a library, you should point to what the new library is and explain what is going on. Not to mention, now there is no valid grunt-contrib-eslint anymore, which drops the credibility of this tool immediately in the mind of users such as myself, despite being authored by the same person.
Also, accessing the repo for grunt-contrib-eslint simply forwards me to this repo. It's disorienting and confusing.
A little more info would go a long way to guiding your users into moving forward to the new convention.
The text was updated successfully, but these errors were encountered:
I've just found this package being used in our setup and I don't have any clue what it does. Done by people long gone :/ So a bit of an explanation what this does would be appreciated indeed.
What is the difference between this project and the grunt-contrib-eslint?
The readme contains absolutely no information about the difference, but the npm install results for grunt-contrib-eslint say it's been deprecated and I should now install this.
If you're going to deprecate a library, you should point to what the new library is and explain what is going on. Not to mention, now there is no valid
grunt-contrib-eslint
anymore, which drops the credibility of this tool immediately in the mind of users such as myself, despite being authored by the same person.Also, accessing the repo for grunt-contrib-eslint simply forwards me to this repo. It's disorienting and confusing.
A little more info would go a long way to guiding your users into moving forward to the new convention.
The text was updated successfully, but these errors were encountered: