Background tasks not showing output

brianchance commented 8 years ago

Installed product versions

Visual Studio: 2015 Professional Update 3 (same behavior on Update 2) NPM Task Runner: 1.3.62

Description

I am using webpack with the awesome-typescript-loaders "forkChecker" feature. In watch mode, this runs the typescript checks in a background thread, then outputs any errors to the console. In the task runner window, the errors never show...

Expected behavior

When run from the command line, it produces this output. (the error is in a horrible red)

Steps to recreate

angular2-webpack-starter uses awesome typescript loader. To get an error, just remove a comma from an import and save. so, in src/main.browser.ts change import { ENV_PROVIDERS, decorateComponentRef } from './platform/environment'; to import { ENV_PROVIDERS decorateComponentRef } from './platform/environment';

scottaddie commented 8 years ago

@brianchance This is a bug in Task Runner Explorer itself, as described here: https://github.com/aspnet/Tooling/issues/600. I have the same problems when using certain Webpack loaders/plugins which write to the console.

madskristensen commented 8 years ago

Errors and warnings should be piped to the TRX correctly in the just-released ASP.NET Core tooling Preview 2

brianchance commented 8 years ago

Thanks all, I will install the update when it comes out.

madskristensen commented 8 years ago

It is out already. Get it here https://www.microsoft.com/net/download#tools

brianchance commented 8 years ago

That did the trick. Only issue now is how webpack uses the --progress switch. In the task runner, the percentages do not overwrite the line, just append to output. Not really necessary so just turning it off.

scottaddie commented 8 years ago

@brianchance That's another feature Task Runner Explorer doesn't support. I've mentioned it to Mads in the past, so I know his team is well aware.

madskristensen / NpmTaskRunner