eslint-plugin-import
Advanced tools
Comparing version 0.5.1 to 0.5.2
{ | ||
"name": "eslint-plugin-import", | ||
"version": "0.5.1", | ||
"version": "0.5.2", | ||
"description": "Import with sanity.", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -8,2 +8,4 @@ eslint-plugin-import | ||
**IF YOU ARE USING THIS WITH SUBLIME**: see the [bottom section](#sublimelinter-eslint) for important info. | ||
**Current support**: | ||
@@ -163,1 +165,34 @@ | ||
to see it grow to become more than just that. | ||
## SublimeLinter-eslint | ||
Recently, SublimeLinter-eslint introduced a change to support `.eslintignore` files | ||
which altered the way file paths are passed to ESLint when linting during editing. | ||
See roadhump/SublimeLinter-eslint#58 for more details, but essentially, you may find | ||
you need to add the following to a `.sublimelinterrc` file: | ||
```json | ||
{ | ||
"linters": { | ||
"eslint": { | ||
"args": ["--stdin-filename", "@"] | ||
} | ||
} | ||
} | ||
``` | ||
I also found that I needed to set `rc_search_limit` to `null`, which removes the file | ||
hierarchy search limit when looking up the directory tree for `.sublimelinterrc`: | ||
In Package Settings / SublimeLinter / User Settings: | ||
```json | ||
{ | ||
"user": { | ||
"rc_search_limit": null | ||
} | ||
} | ||
``` | ||
I believe this defaults to `3`, so you may not need to alter it depending on your | ||
project folder max depth. |
@@ -42,6 +42,12 @@ 'use strict' | ||
// ignore node modules by default | ||
test({ code: 'import { foo } from "crypto"' }) | ||
test({ code: 'import { foo } from "crypto"' }), | ||
test({ code: 'import { someThing } from "./module"' }) | ||
], | ||
invalid: [ | ||
test({ code: 'import { somethingElse } from "./module"' | ||
, errors: [ error('somethingElse', './module') ] | ||
}), | ||
test({ code: 'import { foo } from "crypto"' | ||
@@ -48,0 +54,0 @@ , args: [2, 'all'] |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
37131
738
197