-
Notifications
You must be signed in to change notification settings - Fork 49
no-import-test-files incorrectly flags modules that end in .js #215
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
@IssueHunt has funded $30.00 to this issue.
|
Hi @mearns, I cannot reproduce your issue. Could you tell which version of Thanks |
Sure, you can clone this repo and checkout the "eslint-plugin-ava-215" branch: https://github.com/mearns/lowlight/tree/eslint-plugin-ava-215, then run "npm run format". It runs
Note that this is with eslint-plugin-ava version 5.1.1 |
@sindresorhus has rewarded $27.00 to @GMartigny. See it on IssueHunt
|
Uh oh!
There was an error while loading. Please reload this page.
Using all the default options, the following line in a test file is incorrectly flagged as violating the no-import-test-files rule:
It appears that any module name ending in
.js
will similarly be flagged as a violation. However, the semantics for node'srequire
function will only look for local files if they start with a dot, so this will always be importing a module, not a test file.The text was updated successfully, but these errors were encountered: