-
Notifications
You must be signed in to change notification settings - Fork 54
avn-nvm jshint failures #66
Comments
(avn may want to move to eslint; jshint isn't up to par anymore) |
Sorry, I misinterpreted this. It's actually |
It looks like all of the issues being caught by |
jscs is also deprecated; its team and rules were absorbed into eslint over a year ago. |
This fixes the failures in noted in wbyoung/avn#66, but is really just a temporary solution before moving to ESLint.
@duckontheweb yes, it'd be great to have If you're interested in making those changes, the help would be much appreciated! 😄 |
Definitely. I'll open up separate issues for each of these. |
Resolved by wbyoung/avn-nvm@fd47799, but @duckontheweb is also working on transitioning to ESLint. See #67. |
Please describe your issue clearly and also include all details below.
Details
v4.8.6
I'm getting a number of
jshint
failures when running the tests foravn-nvm
, all of them in/index.js
(see below for full details). Would you like me to clean these up before submitting any PRs related to #43?The text was updated successfully, but these errors were encountered: