Real-time ImportLint diagnostics for
TypeScript and JavaScript, powered by the import-lint lsp language server.
ImportLint enforces @package/@private JSDoc import-access rules (a port of
eslint-plugin-import-access)
so that modules can restrict who is allowed to import them — including
detecting violations introduced in files you haven't even opened yet.
Requirements
This extension is a thin client: it does not bundle a linter binary. It looks
for one in this order:
The importLint.binaryPath setting, if set.
@import-lint/cli installed in the workspace's node_modules
(npm install -D @import-lint/cli).
import-lint on your PATH (e.g. installed via cargo install import-lint).
The resolved binary must be version 0.1.2 or later (the first release with
the lsp subcommand); older binaries are detected and rejected with a clear
notification rather than failing silently.
Settings
Setting
Default
Description
importLint.enabled
"auto"
"auto" starts the server only when a .importlintrc.json(c) exists in the workspace; "on" always starts it; "off" never starts it.
importLint.run
"onType"
"onType" lints on every keystroke; "onSave" lints only on save.
importLint.binaryPath
""
Absolute path to an import-lint binary. Overrides automatic resolution.
importLint.trace.server
"off"
Standard vscode-languageclient trace level (off | messages | verbose) for debugging the LSP connection.
Commands
ImportLint: Restart Server (importLint.restart) — stops and
re-locates/restarts the server. Use this after npm installing a different
@import-lint/cli version, or after changing importLint.binaryPath.
Learn more
See the ImportLint repository for
configuration (.importlintrc.json), rule documentation, and release notes.
