v0.1.7

New: suppress a violation with a directive comment

You can now acknowledge a violation at the import site without fixing it (yet) — the ImportLint equivalent of ESLint's eslint-disable-next-line:

// import-lint-disable-next-line -- migrating gradually, see #123
import { issueToken } from "../auth/token";

import { issueToken } from "../auth/token"; // import-lint-disable-line

import-lint-disable-next-line suppresses diagnostics on the following line; import-lint-disable-line suppresses them on its own line. Both work as // line comments or /* ... */ block comments. A bare directive suppresses everything on the target line; an optional rule-name list restricts it (package-access for access violations, unresolved for --report-unresolved warnings). Anything after a -- separator is a free-form justification, ignored by the parser. Directives match lines, so in a multiline import statement, place the directive inside the braces, directly above the violating specifier.

Migrating from eslint-plugin-import-access: replace // eslint-disable-next-line import-access/jsdoc with // import-lint-disable-next-line. See Suppressing a violation with a comment in the README; the built-in docs (import-lint docs fixing, import-lint explain) and the agent skill cover the new directives too.

Lint behavior is unchanged for code that contains no directives — checking and output are identical to v0.1.6 otherwise.

Full Changelog: v0.1.6...v0.1.7