Registry / testing / xlint
library0.2.2jsnpmunverified

A powerful CLI tool for running any lint solution (JSLint, JSHint, etc.) on JavaScript files. It recursively scans .js and executable Node.js files, supports external configuration files (.lint), understands .gitignore and .lintignore rules, includes optional caching and live console updates via --watch. The current stable version is 0.2.2, released with basic Node.js support (>=0.8) and minimal dependencies. It is a niche tool with limited maintenance; alternatives like ESLint are more modern and widely adopted.

npm install xlint
INSTALL
IMPORT
SIG · XLINT
X
xlint
testingjavascriptv0.2.2
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

xlint (CLI)
npm install -g xlint
npm install xlint (local install rarely useful)
xlint is primarily a CLI tool, not a library to import programmatically.

Global install, create a project with a test JS file, configure .lint, and run xlint with a linter path.

npm install -g xlint mkdir -p myproject && cd myproject echo 'var x = 1;' > test.js echo '{"linter": "path/to/jslint.js"}' > .lint xlint --linter=path/to/jslint.js --depth=Infinity .
xlint --version
Debug
Known issues
deprecatedxlint is no longer actively maintained. Consider using ESLint or other modern linters.
fix
Migrate to ESLint or a maintained alternative.
affects: >=0.0.0
gotchaRequires a separate linter module (e.g., xlint-jslint). Without one, xlint cannot lint anything.
fix
Install a linter module like 'npm install xlint-jslint' and pass its path.
affects: >=0.0.0
gotchaDefault linter is not provided. You must specify --linter option or configure it in .lint file.
fix
Always provide --linter=... or set 'linter' in .lint configuration file.
affects: >=0.0.0
gotchaConfiguration files (.lint) use a custom format similar to UNIX conf files, not JSON. Syntax errors may cause silent failures.
fix
Validate .lint file syntax carefully; use comments starting with # and key-value pairs.
affects: >=0.0.0
Errors
Common errors & fixes
Error: Cannot find module 'path/to/jslint-module.js'
Invalid --linter path or missing linter module.
fix
Install a valid linter module (e.g., xlint-jslint) and provide correct absolute or relative path.
xlint: Neither specified linter was provided, nor default could be resolved
No --linter argument and no linter set in .lint configuration.
fix
Add --linter option or create a .lint file with 'linter' key pointing to a valid linter module.
No files to lint
No JavaScript files found in the target directory or all files ignored via .gitignore/.lintignore.
fix
Ensure target directory contains .js files or executable Node.js files not ignored by ignore rules.
Upgrade
Version history
0.2.2latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
19 hits · last 30 days
node
18
Resources
xlint — npm install xlint · libregistry