TSSLint

A lightweight inspection tool that seamlessly integrates with TypeScript Language Server

TSSLint is not your typical linter. Its main purpose is to expose the TypeScript Language Server diagnostic interface, allowing you to add your own diagnostic rules without additional overhead to creating a TypeChecker.

Discord Server: https://discord.gg/NpdmPEUNjE

Special thanks to @basarat for transferring the tsl package name.

Packages

This repository is a monorepo that we manage using Lerna-Lite. That means that we actually publish several packages to npm from the same codebase, including:

• cli: This package provides the command line interface for TSSLint.
• config: This package allows you to define and build configuration files for TSSLint.
• core: This is the core package for TSSLint, which provides the main functionality of the tool.
• typescript-plugin: This package integrates TSSLint with the TypeScript language server.
• vscode: This package is a Visual Studio Code extension that integrates TSSLint into the editor.

Why TSSLint?

The performance of TypeScript in code editors has always been a crucial concern. Most TypeScript tools integrate TypeScript libraries to enable type checking and query code types through the LanguageService or TypeChecker API.

However, for complex types or large codebases, the tsserver process can consume significant memory and CPU resources. When linter tools integrate with TypeScript and create their own LanguageService instances, memory and CPU usage can continue to increase. In some cases, this has caused projects to experience long save times when codeActionOnSave is enabled in VSCode.

TSSLint aims to seamlessly integrate with tsserver to minimize unnecessary overhead and provide linting capabilities on top of it.

Features

• Integration with tsserver to minimize semantic linting overhead in IDEs.
• Writing config in typescript.
• Direct support for meta framework files based on TS Plugin without a parser. (e.g., Vue, MDX)
• Pure ESM.
• Supports HTTP URL import, no need to add dependencies in package.json.
• Designed to allow simple, direct access to rule source code without an intermediary layer.

Usage

To enable TSSLint in VSCode, follow these steps:

1. Install the TSSLint VSCode Extension
2. Add the @tsslint/config dependency to your project.

   {
   	"devDependencies": {
   		"@tsslint/config": "latest"
   	}
   }

3. Create the tsslint.config.ts config file:

   import { defineConfig } from '@tsslint/config';
   
   export default defineConfig({
   	rules: {
   		// ... your rules
   	},
   });

Create a Rule

To create a rule, you need to define a function that receives the context of the current diagnostic task. Within this function, you can call reportError() or reportWarning() to report an error.

As an example, let's create a no-console rule under [project root]/rules/.

Here's the code for [project root]/rules/noConsoleRule.ts:

import { defineRule } from '@tsslint/config';

export function create() {
	return defineRule(({ typescript: ts, sourceFile, reportWarning }) => {
		ts.forEachChild(sourceFile, function cb(node) {
			if (
				ts.isPropertyAccessExpression(node) &&
				ts.isIdentifier(node.expression) &&
				node.expression.text === 'console'
			) {
				reportWarning(
					`Calls to 'console.x' are not allowed.`,
					node.parent.getStart(sourceFile),
					node.parent.getEnd()
				).withFix(
					'Remove this console expression',
					() => [{
						fileName: sourceFile.fileName,
						textChanges: [{
							newText: '/* deleted */',
							span: {
								start: node.parent.getStart(sourceFile),
								length: node.parent.getWidth(sourceFile),
							},
						}],
					}]
				);
			}
			ts.forEachChild(node, cb);
		});
	});
}

Then add it to the tsslint.config.ts config file.

import { defineConfig } from '@tsslint/config';

export default defineConfig({
	rules: {
+ 		'no-console': (await import('./rules/noConsoleRule.ts')).create(),
	},
});

After saving the config file, you will notice that console.log is now reporting errors in the editor. The error message will also display the specific line of code where the error occurred. Clicking on the error message will take you to line 11 in noConsoleRule.ts, where the reportWarning() code is located.

Full example: https://github.com/johnsoncodehk/tsslint/tree/master/fixtures/define-a-rule

Import Rules from HTTP URL

You can directly import rules from other repositories using HTTP URLs. This allows you to easily share and reuse rules across different projects.

Here's an example of how to import a rule from a HTTP URL:

import { defineConfig } from '@tsslint/config';

export default defineConfig({
	rules: {
		'no-console': (await import('./rules/noConsoleRule.ts')).create(),
+ 		'no-alert': (await import('https://gist.githubusercontent.com/johnsoncodehk/55a4c45a5a35fc30b83de20507fb2bdc/raw/5f9c9a67ace76c0a77995fd71c3fb4fb504a40c8/TSSLint_noAlertRule.ts')).create(),
	},
});

In this example, the no-alert rule is imported from a file hosted on GitHub. After saving the config file, you will notice that alert() calls are now reporting errors in the editor.

Full example: https://github.com/johnsoncodehk/tsslint/tree/master/fixtures/http-import

Modify the Error

While you cannot directly configure the severity of a rule, you can modify the reported errors through the resolveDiagnostics() API in the config file. This allows you to customize the severity of specific rules and even add additional errors.

Here's an example of changing the severity of the no-console rule from Warning to Error in the tsslint.config.ts file:

import { defineConfig } from '@tsslint/config';
import noConsoleRule from './rules/noConsoleRule.ts';

export default defineConfig({
	rules: {
		'no-console': noConsoleRule
	},
	plugins: [
		({ typescript: ts }) => ({
			resolveDiagnostics(_fileName, diagnostics) {
				for (const diagnostic of diagnostics) {
					if (diagnostic.code === 'no-console') {
						diagnostic.category = ts.DiagnosticCategory.Error;
					}
				}
				return diagnostics;
			},
		}),
	],
});

CLI Usage

The @tsslint/cli package provides a command-line interface for running the TSSLint tool across your TypeScript projects. It can be used by running the tsslint command in your terminal.

Here is a basic example of how to use it:

npx tsslint --project ./path/to/your/tsconfig.json

This command will run the linter on the TypeScript project defined by the provided tsconfig.json file. Any linting errors will be output to the console.

If you want to automatically fix any fixable linting errors, you can use the --fix option:

npx tsslint --project ./path/to/your/tsconfig.json --fix

This will run the linter and automatically apply any fixes that are available.

You can also lint multiple projects at once by using the --projects option:

npx tsslint --projects './packages/*/tsconfig.json'

This command will run the linter on all TypeScript projects located in the subdirectories of the packages directory. Each subdirectory should contain a tsconfig.json file defining a TypeScript project. Any linting errors will be output to the console.