Package Exports
- eslint-plugin-import
- eslint-plugin-import/lib/rules/default
- eslint-plugin-import/lib/rules/named
- eslint-plugin-import/package.json
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-plugin-import) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
eslint-plugin-import
This plugin intends to support linting of ES6 import syntax, and prevent issues with misspelling of file paths and import names. All the goodness that the ES6 static module syntax intends to provide, marked up in your editor.
Current support:
- Ensure imports point to a file/module that exists. (
exists) - Ensure named imports correspond to a named export in the remote file. (
named) - Ensure a default export is present, given a default import. (
default) - Report ES6 import of CommonJS modules. (
no-common) - Ensure imported namespaces contain dereferenced properties as they are dereferenced. (
namespace) - Report assignments (at any scope) to imported names/namespaces. (
no-reassign)
Rules
exists
Ensures an imported module exists, as defined by standard Node require.resolve behavior.
named
Verifies that all named imports are part of the set of named exports in the referenced module.
Note that if there are no named exports, nor a default export, this rule will not report a mismatch, to allow Babel-style import of CommonJS modules.
Provide the es6-only option in your rule config if you would like to enforce this on all imports.
default
If a default import is requested, this rule will report if there is no default export in the imported module.
Note that if there are no named exports, nor a default export, this rule will not report a mismatch, to allow Babel-style import of CommonJS modules.
Provide the es6-only option in your rule config if you would like to enforce this on all imports.
no-common
Report for imports that are defined as CommonJS modules, identified by the presence of module.exports or exports[...] assignments within the module. Off by default.
namespace
Enforces names exist at the time they are dereferenced, when imported as a full namespace (i.e. import * as foo from './foo'; foo.bar(); will report if bar is not exported by ./foo.).
If remote module is CommonJS, will not attempt to enforce.
Will report at the import declaration if there are no exported names found.
Also, will report for computed references (i.e. foo["bar"]()).
Implementation note: currently, this rule does not check for possible redefinition of the namespace in an intermediate scope. Adherence to the ESLint no-shadow rule for namespaces will prevent this from being a problem.
no-reassign
Reports on assignment to an imported name (or a member of an imported namespace). Does not consider scope or shadowing, so failure to adhere to ESLint's no-shadow may result in spurious warnings.