-
Notifications
You must be signed in to change notification settings - Fork 384
Eslint gives errors/nothing when run with npm and Rake #364
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
Comments
@reconstructions It would be great to get the linter updated (the npm package, a PR would be great ), as well as to update this repo. I'm looking for somebody to help me with the update to Webpack 2! #336 |
Sounds great, I have a commit which gets Eslint to green with minimal changes to the app, I will try to make sure that is ready for a PR. I also have a couple of months worth of small enhancements which might bolster this repo, for example setting all the ports in an .env file, 12 factor app number 3 style. Plus some extra test coverage which has made it easier for me to refactor the app. I will start taking a look at Webpack 2 and see if I am fit to contribute there... |
@reconstructions Any update? |
Thanks @justin808, I submitted PR #368 which gets Eslint to green a couple days ago, @kaizencodes thought his #336 might also fix this, I was going to merge #336 into a couple of my apps and see how that works, I will let you know. |
When the 'lint' script in package.json is run with
npm run lint
, it gives 82 linting errors.Running the
rake lint:eslint
task gives something like this:But that's it.
Assuming that the Rake task isn't working, are these real linting errors given your "eslint-config-shakacode" package? If so, I will fix them, let me know if it would make sense to try and fix them here.
The text was updated successfully, but these errors were encountered: