-
Notifications
You must be signed in to change notification settings - Fork 16
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
Linting normal .js files is really slow #4
Comments
As of now there is no way to do this. /**
* @jsx React.DOM
*/ and only run the file trought the transformer if this is the case. Or it could check if the file has a |
We're not fans of adding that comment at the top, as our internal naming convention of keeping the If there was a split code path based on the file extension that would fit our use case perfectly. I haven't been working with jsx long enough to know any other use cases yet. |
ok. I will add the split code path based on the file extension. |
Awesome! |
I added the check for the file extension. Now only |
Thanks. I'll update when I get back at work in the morning :) |
I'm guessing everything is run through the transformer as it is.
I have thousands of files that aren't jsx yet. Plugging in grunt-jsxhint as a drop in replacement considerably slows down my linting.
Any way to be able to tell the linter which files should be transformed and which should pass through untouched?
The text was updated successfully, but these errors were encountered: