jsrules | JavaScript rule engine that models | Rule Engine library

Here's what's happening:

1. typescript-eslint uses your tsconfig.json file to read in a collection of source files
2. ESLint rules use the TypeScript features provided by typescript-eslint
3. Those ESLint rules are being run on a file that's not included in your tsconfig.json

This causes a crash because TypeScript information is being requested about a file that TypeScript doesn't know about.

Make sure your ESLint file is set to only run on files included in your tsconfig.json, and this error should go away.

try excluding like this as mentioned in webpack docs

As mentioned in this github issue, TSLint ignores .d.ts files when processing the include paths from tsconfig.json.

Unfortunately, TSLint is not in development anymore so this will never be changed. The official suggestion is to use ESLint with typescript-eslint instead. You can read more about that in this blog post.

If you'd like to keep using TSLint for the time being, you could specify both paths when calling it like this:

It looks like the "as-needed" option was added in tslint@5.4.0.

To get it to work, update tslint to that version (by running npm i -D tslint@^5.4.0, or however else you like to update your dependencies).

Note this crosses a major version bump so there may be breaking changes.

The "documentation must exist" complaint you're seeing is from TSLint (not TypeScript). // @ts-ignore only applies to TypeScript complaints (not TSLint) so that won't help with it.

Instead, you have a couple options:

• Disable the completed-docs rule in your tslint.json file with a "completed-docs": false inside the "rules" object (docs)
• Use // tslint:disable-next-line:completed-docs (docs)

For context, TSLint and TypeScript are two separate tools. TypeScript is the language that converts your .ts/.tsx files to .js; TSLint uses TypeScript to scan your code for issues.

As to why you're seeing different TSLint behavior across different projects, perhaps your versions are different? TSLint 5.13 changed how completed-docs runs compared to 5.12.

It's unfortunately a known issue with tslint-microsoft-contrib. The react-unused-props-and-state rule does not work with stateless functional components (SFCs). One fix is to use stateful components (classes) instead.

https://github.com/Microsoft/tslint-microsoft-contrib/issues/339

You're looking for the type-literal-delimiter rule. Just change it from false to true in your tslint.json.

Try to reinstall vscode. And select 'no and never' button when you change name file it will show the pop up look like this "Automatically update imports for moved file"

https://github.com/Microsoft/vscode/issues/53832

This is a simple syntax error. The template should he a multiline string literal, which is enclosed by backticks (`) instead of single quotes.