Error with Version 3.0.8

[kcsahoo]

I am using V 3.0.8 with Typescript 2.1.1
I am getting error:
Module Build Failed : Error: Final loader didn't return a Buffer or String

The same error throws with any V 3 and Typescript 2.1,x

It works with V 2.2.4 and Typescript 2.0.10

ts-loader does not have problem with Typescript 2.2.1

Can this be fixed please.
Note - I have installed all loaders advised in different forums.

[jonrimmer]

Is every loader name in your webpack.config.js suffixed with "-loader"? This is a requirement in Webpack 2, and can cause the error you're getting. E.g.

  loaders: ['ng-annotate', 'awesome-typescript']

Is no longer valid. It must be:

  loaders: ['ng-annotate-loader', 'awesome-typescript-loader']

[RafaelSalguero]

I have the same problem, the loaders names are correct on my project

[giniedp]

this is what i am getting during compilation since version 3.0.8

[at-loader]: Child process failed to process the request:  TypeError: Cannot read property 'path' of undefined
    at /Users/alex/repositories/gebeco/gbc3/node_modules/typescript/lib/typescript.js:43764:45
    at Map.forEach (native)
    at createResolver (/Users/alex/repositories/gebeco/gbc3/node_modules/typescript/lib/typescript.js:43759:49)
    at Object.createTypeChecker (/Users/alex/repositories/gebeco/gbc3/node_modules/typescript/lib/typescript.js:24712:28)
    at Object.getTypeChecker (/Users/alex/repositories/gebeco/gbc3/node_modules/typescript/lib/typescript.js:64254:79)
    at synchronizeHostData (/Users/alex/repositories/gebeco/gbc3/node_modules/typescript/lib/typescript.js:81190:21)
    at Object.getProgram (/Users/alex/repositories/gebeco/gbc3/node_modules/typescript/lib/typescript.js:81272:13)
    at processInit (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/checker/runtime.ts:264:33)
    at /Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/checker/runtime.ts:460:21
    at Object.send (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/checker/runtime.ts:27:21)
    at Checker.req (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/checker/checker.ts:101:21)
    at new Checker (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/checker/checker.ts:80:14)
    at Object.ensureInstance (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/instance.ts:129:21)
    at compiler (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/index.ts:45:22)
    at Object.loader (/Users/alex/repositories/gebeco/gbc3/node_modules/awesome-typescript-loader/src/index.ts:14:18)
    at LOADER_EXECUTION (/Users/alex/repositories/gebeco/gbc3/node_modules/loader-runner/lib/LoaderRunner.js:119:14)

[vincentw56]

Same problem here. I double-checked my loader names, Now I cannot get it to build.

[RafaelSalguero]

I fixed my problem by having the same case on the requires and on the file and folder names. This is problematic since my enviroment is case-insensitive

[vincentw56]

I am using Windows so case shouldn't matter. It has never been an issue before. This has been working fine for me until just today. I switched to ts-loader and everything works fine. It is slower, but at least I can do my work.

[szahn]

Same problem. in Windows. Using Webpack 2.2.1, Typescript 2.1.5 awesome-typescript-loader 3.0.8.

I realized this error was the result of a require statement referencing a file with incorrect casting in a case-insensitive OS (like Windows). It would be great if the error message was more precise. Can it check for mismatches in file casing?

[vincentw56]

Looks like this is fixed in version 3.1.2.

[kcsahoo]

No
I am using Awesome 3.1.2 and Typescript 2.2.1
I am getting the following error:
Module build failed:Error:Final loader didn't return a Buffer or String
I am using Windows.

Everything works with combination:
Awesome 2.2.4 and Typescript 2.1.1/2.0.10

With Typescript 2.2.1 and ts-loader, no problem.

[kcsahoo]

I am using webpack 2.2.1 if it helps to identify the issue

[kcsahoo]

Issue resolved with Awesome 3.1.2 and Typescript 2.2.1.
I had duplicate tsconfig.json with non-matching entries.
Removed duplicate and the error disappeared.

[kcsahoo]

No I am wrong.
It still does not work and has the same error.
Only works with ATL V2.2.4 and Typescript 2.1.1/2.0.10

[vincentw56]

I am running Webpack 2.2.1, Typescript 2.2.1, and Awesome Typescript Loader 3.1.2 with no issues. Try deleting your .awcache folder. I've found sometimes that fixes some issues with Awesome Typescript Loader.

[kcsahoo]

Where is .awcache folder?
I cannot find in node_modules folder.

[vincentw56]

It is not in the node_modules folder. It should be in the root or same folder level as the node_modules level. That is how it is on all my projects on Windows.