Richard G Richard G - 5 months ago 24
TypeScript Question

How to setup VSCode to show typescript error inline

I'm trying to migrate an ES6 project to typescript. This is my first attempt at writing a typescript module in NodeJS.

It seems to work better in Angular-CLI so far.

I've got it compiling using command line

, but I'm not sure how to display errors and intellisense in the code editor?

In a directory I have the two files shown below. When it compiles it, as expected throws a compile error:
Supplied parameters do not match any signature of cal
l target.
. This is fine.

But VSCode is not showing any errors in the editor, even if I make a deliberate syntax error like taking out a bracket, or type errors like this one. How do I get VSCode to show inline syntax or compiler errors in the editor for .ts files?


* Wrapper for a particular validation error.
export class ValidationError extends Error {
private type: string;

constructor(error: any) {
Error.captureStackTrace(this, this.constructor);
this.message = error.message;
this.type = 'ValidationError';

Then I'm trying to write simple spec to test out the workflow:


import { ValidationError } from './validation-error';
import * as should from 'should';

describe('Validation Error', () => {
it('should create a new instance', () => {
const instance = new ValidationError();

Edited Here:

I'm still plugging away at this - I've setup
to run automatically with this job in

// See
// for the documentation about the tasks.json format
"taskName": "tsc",
"command": "tsc",
"isShellCommand": true,
"args": ["-w", "-p", "."],
"problemMatcher": "$tsc-watch",
"echoCommand": true

I suspect that if the errors were reported properly using
, the error would probably also show up in the editor. When I run the task I get output like:

running command$ tsc -w -p .
src/hello.ts(15,1): error TS2346: Supplied parameters do not match any signature of call target.
4:24:40 PM - Compilation complete. Watching for file changes.

But there are no problems reported in the
view - even though clearly there's a compiler issue.

Got the
setting from this page of the docs:

Answer Source

Even without having installed TypeScript locally or globally, the following setup provides inline errors.



let x: number;
x = "foo";


{ }

Here is a screenshot that shows the inline error in x.

enter image description here

Please try that setup and report back on what happens.