-
Notifications
You must be signed in to change notification settings - Fork 71
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
JsxHint support #91
Comments
I've also started doing some work with react, and this feature would be great. Since jsxhint is meant for use from command line and doesn't export function to lint any given text as parameter, i think it would be better and faster to just quickly compile temporary input file with react-tools before running jshint on the text.
If i'd find some spare time, I will prepare a possible solution as a pull request (if noone will do it till then :)) |
I submitted pull request #99 for this. |
Oh yes, that would be neat. Any news on merging the above PR? |
This will never happen, because jsxHint is now deprecated. |
deprecated? what else should we use instead? what's its official replacement? |
@binarykitchen I switched to eslint and using https://github.com/roadhump/SublimeLinter-eslint |
ok, and how do i migrate .jshintrc to .eslintrc ? |
It would be great to add possibility of linting JSX (ReactJS markup) files. I would consider as an option to specify path to jshint package and set it to https://www.npmjs.org/package/jsxhint which is "A wrapper around JSHint to allow linting of files containing JSX syntax."
The text was updated successfully, but these errors were encountered: