at-loader does not display checking errors

[johnbendi]

at-loader just leaves me with the following ambiguous error message:

[at-loader] Checking started in a separate process...

[at-loader] Checking finished with 5 errors

[AlexGalays]

I have the same issue with the latest version (3.0.0-beta.18) and webpack 2.2 rc3.

It always works the very first time, and sometimes it continues to work for a while but once it get stuck with the above message, I have to restart the watch. That's a big blocker.

[kristaps]

May be something different but when using watch I get a listing of all errors on the first compile, and only the "finished with x errors" summary on subsequent compiles.

[kristaps]

Versions: awesome-typescript-loader@3.0.0-beta.18, typescript@2.1.5, anything else that could help?

[tony-gutierrez]

+1, this is killing me.

[AlexGalays]

ts-loader works just fine with webpack 2 by the way, if you're stuck.

[coffius]

+1

I can see error detail in browser console.

[erikstoff]

+1

[s-panferov]

Hello everybody, could you please try the latest version? Or could someone please create a repo? I have output tests and everything seems to work fine.

[jvanbruegge]

For me it happens only with the webpack 2 node API, with the cli everything works fine

[s-panferov]

If you run webpack by hand, the loader acts in non-watch mode and simply pushes all the errors to webpack.

https://github.com/s-panferov/awesome-typescript-loader/blob/master/src/instance.ts#L380-L384

You should expect to see the errors in webpack stats.

[dannypule]

Getting same issue "[at-loader] Checking finished with 12 errors". Doesn't show a list of errors in the command line. Only shows me what the errors are when I run. In my case, certain dependencies hadn't been installed (angular 2 cookie and redux) because I had done this before updating my angular starter applications package.json from it's original repo.

In other words: run your app on localhost and check whats in the console. Might give some clues.

[samal-rasmussen]

I had transpileOnly: true in my at-loader options. Changed it back to false, and got the errors back.

[davidmoshal]

+1